[Rd] Segmentation fault, devPS.c, 0.99.0 (PR#413)

Peter Dalgaard BSA
2000-02-07T22:44:42Z

Roger.Bivand@nhh.no writes:

> Full_Name: Roger Bivand
> Version: 0.99.0
> OS: RH Linux 6.1
> Submission from: (NULL) (158.37.60.152)
...
> #0  0x4021df2a in _IO_vfprintf (s=0x726b2e78, format=0x811ad81
"ep\n",
>     ap=0xbfffde18) at vfprintf.c:1024
> 1024	vfprintf.c: No such file or directory.
> #1  0x40225f47 in fprintf (stream=0x726b2e78, format=0x811ad81
"ep\n")
>     at fprintf.c:32
> 32	fprintf.c: No such file or directory.
> (gdb) up
> #2  0x806ca78 in PostScriptEndPage (fp=0x726b2e78) at devPS.c:513
> 513	    fprintf(fp, "ep\n");
> (gdb) up
...
> The examples do use MASS, spatial, akima, and modreg, and the first three
of
> these
> have been REMOVEd and freshly INSTALLed, just in case, but the problem
appears
> to
> be in the postscript output. If you might find it useful to see the code, I
> could
> make it available, but I don't think that you really need (!) to
install GRASS,
> unless
> you know definitely that you do!

Hmm. This looks a bit nasty. You're hitting a segmentation fault
inside of an fprintf call, which likely means either that you're badly
out of memory (not really likely) or that the FILE structure "stream"
(alias "s" alis "fp" at 0x726b2e78) has gotten corrupted.

If you run the same example under the debugger, you might go in and
see what got corrupted (run till crash then "up", "up",
"p *fp" to get
started) and see at what point in the execution it happened (this is
what gdb's hardware watchpoints are for...).

--
   O__  ---- Peter Dalgaard             Blegdamsvej 3
  c/ /'_ --- Dept. of Biostatistics     2200 Cph. N
 (*) \(*) -- University of Copenhagen   Denmark      Ph: (+45) 35327918
~~~~~~~~~~ - (p.dalgaard@biostat.ku.dk)             FAX: (+45) 35327907