Loading ...
Sorry, an error occurred while loading the content.

segfault in 2.32 when script name is too long

Expand Messages
  • Andrew Schulman
    ploticus segfaults when the name of its input script file is too long: $ ploticus
    Message 1 of 1 , Dec 30, 2005
    • 0 Attachment
      ploticus segfaults when the name of its input script file is too long:

      $ ploticus /public/data/oecau07a/web/otis/testpqk/pcseffluents/temp/pcseffluents/PA0002437.101.34247.1.1.20020701.20050630.small.plo -png -o /public/data/oecau07a/web/otis/testpqk/pcseffluents/temp/pcseffluents/PA0002437.101.34247.1.1.20020701.20050630.small.png -csmap -mapfile /public/data/oecau07a/web/otis/testpqk/pcseffluents/temp/pcseffluents/PA0002437.101.34247.1.1.20020701.20050630.small.map
      Segmentation fault

      $ ploticus ~/script.plo -png -o /public/data/oecau07a/web/otis/testpqk/pcseffluents/temp/pcseffluents/PA0002437.101.34247.1.1.20020701.20050630.small.png -csmap -mapfile /public/data/oecau07a/web/otis/testpqk/pcseffluents/temp/pcseffluents/PA0002437.101.34247.1.1.20020701.20050630.small.map

      $

      The only difference between these two commands is the name of the first argument,
      which is obviously much shorter in the second case. The two script files are
      identical; the second is in fact a symlink to the first.

      It might seem that the path names in this example are ridiculously long, and I
      won't deny it. But they're automatically generated by a script. In any
      case ploticus certainly shouldn't segfault over it.

      For now my workaround is to change the process working directory so that the
      path names are shorter.

      Andrew.
    Your message has been successfully submitted and would be delivered to recipients shortly.