On Tue, May 09, 2000 at 12:57:46AM +0000, Rob Lahaye wrote:
> 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):
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x401e0688 in HandleActions () from /usr/X11R6/lib/libXt.so.6
>
>
> 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?
> 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?
[...]
Hi,
some remarks debugging (parts may be in the LessTif docs already,
e.g. bugs.html, but I'll add missing stuff):
- build/install a debugging version of lesstif (see configure flags)
- build application with debugging support (i.e. in any case with -g
(if gcc is being used) and disable optimization (-O0))
- start in a debugger (gdb)
- set breakpoint on exit() (if looking for X protocol errors)
- run in synchronous mode (run -sync)
- reproduce bug
- produce a stacktrace (bt)
So far it should be straightforward and easily be adopted even to
"nonGNU" environments.
--
Alexander Mai
[EMAIL PROTECTED]
