On 09-May-00 at 16:42, Rob Lahaye ([EMAIL PROTECTED]) wrote:
The file BUG_REPORTING that comes in the LessTif source distribution can help
here. It describes how to get the info from gdb that we need. I'll add a couple
of comments to this message also, keep scrolling......
> Dear Mr. Hennessy,
>
> Concerning the Grace SIGSEGV when applying the clear-button
> to the "Results" Window:
>
> You asked me to do some debugging since you cannot reproduce
> the problem. First of all I'm not an experienced debugger.
> When I simply do a "gdb xmgrace", without having grace and
> lesstif compiled with a -g option, I get (after performing
> the actions that cause the SIGSEGV):
After the gdb xmgrace, you should start the program with "run -sync".
Explanation in the file I mentioned earlier.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x401e0688 in HandleActions () from /usr/X11R6/lib/libXt.so.6
At the gdb prompt, type "where". This will show the sequece of calls that got
you to this place.
>
>
> Well, then I'm confused, because it complains about libXt.so.6,
> which is from XFree86-libs version 3.3.6-11.
>
> Does this mean that lesstif is NOT the problem, but Grace uses
> wrongly a function from the X11-library?
Not necessarily. The where from above will show how we got here.
> In that case this bugreport should go to the grace-mailing list.
> Or does Lesstif and the X11-library collide here?
>
> Would it be more useful when I compile lesstif AND grace with
> the -g option?
It is always more usefull to use the -g option when you are dealing with gdb.
You get more, and better, information.
>
> My current system is:
>
> RedHat Linux 6.2 PC
> Grace (most recent development) version 20000507
> LessTif (development) version 0.90.3
> XFree86 (official release) version 3.3.6-11
>
> Please send email to me personally, since I'm not member
> of the lesstif mailing list.
>
> Regards,
>
> Rob.
>
>
> C Hennessy wrote:
> >
> > Hi Rob,
> > Sorry but I have never used this tool so I cannot reproduce
> > your problem. If you can either show me how to reproduce this or
> > else give me a backtrace from gdb when the crash is experienced.
> > The best solution is to give us a small code example of where the
> > problem is.
> >
> > Rob Lahaye wrote:
> > >
> > > Dear Mr. Hennessy,
> > >
> > > Lesstif (CVS as of April 13th) shows a bug with Grace;
> > > it's the text field in Window->Results.
> > > The problem does not occur when Grace is compiled
> > > against Motif.
> > >
> > > Do a non-linear-fit to a dataset and the results
> > > are displayed in the Results-text-field (this will
> > > pop up automatically).
> > > Now one can cause Grace to crash with a "Oops! Got SIGSYS"
> > > in two ways:
> > >
> > > 1) Clear the Results-text-field with the <clear> button
> > > and perform again a fit procedure: SIGSYS crash!
> > > However, this is a "slow" crash; it takes almost one
> > > second on my 350MHz PC for Grace to collapse.
> > > (I don't know what's going wrong, but possibly it tries
> > > to write to the Results-text-field, which has been broken
> > > by the <clear operation> ?!?!)
> > >
> > > 2) Use the mouse to mark (color reverse) the text in the
> > > Results-text-field and then click <clear>. Grace will
> > > immediately crash with the SIGSYS.
> > >
> > > Regards,
> > >
> > > Rob.
> > > [EMAIL PROTECTED]
> > > ------------------------------------------------------------------
> > > Grace-5.1.0
> > >
> > > GUI toolkit: @(#)GNU/LessTif Version 1.2 Release 0.89.9 cvs
> > > T1lib: 1.0.1-grace
> > > FFT: built-in
> > > NetCDF support: off
> > > Built: Fri Apr 7 12:26:23 2000 on Linux 2.2.15-2.5.0 i686
> > > Compiler flags: gcc -O2 -mcpu=pentiumpro -fno-common -Wall -pedantic
> > > -Wpointer-arith -Wnested-externs -Wno-implicit-int -I.. -I.
> > > -I../T1lib/t1lib -I/usr/local/lesstif/include -I/usr/X11R6/include
> > > -L/usr/local/lesstif/lib -L/usr/X11R6/lib -lXbae -lXm -lXpm -lXp
> > > -lXmu -lXt -lXext -lX11 -lSM -lICE ../cephes/libcephes.a
> > > ../T1lib/libt1.a -ltiff -ljpeg -lpng -lz -lm -ldl
> > >
> > > Registered devices:
> > > X11 PostScript EPS MIF SVG PNM JPEG PNG Metafile
>
>
