On 18-Jun-00 at 19:14, Jim Lemon ([EMAIL PROTECTED]) wrote:
> Rick Scott wrote:
> >
> ...Oh, wait
> > a minute....."DEBUGSOURCES=all nedit" may show something interesting.
> > Also can you make it happen if you run "nedit -sync"????
> > >
>
> Thanks to both for your replies
>
> I was using the '- sync' option, although I simply copied the command
> line from the 'lesstif bug report' page. I think that may be why the
> system hung up so badly, as NEdit simply disappears when I run it
The problem is that the menu system makes several "server grabs". These
normally get released when the app exits. The problem you are seeing is that
the grab is still in effect, the app is still sort of running when control is
passed to gdb.
> normally. I'm not familiar with 'DEBUGSOURCES=all", but it doesn't seem
> to be an option to gdb. I tried it but it replied:
It has nothing to do with gdb. It is an environment variable that is understood
by LessTif. It is explained somewhere in one of our
README/INSTALL/BUG-REPORTING files, not sure exactly which one.
>
> gdb: unrecognized option `-DEBUGSOURCES=all'
> Use `gdb --help' for a complete list of options.
>
> At this point, I was about to ask for a recipe for running the
> mysterious debugging routine suggested (I am only an ordinary mortal who
> programs in C and a few other languages) when I had a brainwave. I ran
> gdb in KDE's konsole, started nedit and shrank it until I could see the
> whole console window. It took a while to get it to blow up, but I
> finally did it by loading a text file, typing a bit of nonsense,
> including (using Alt-I) another file, then hitting Alt-F. Same result
> as before, right-pointing arrow, no response from anything except
> Ctrl-Alt-BS, and in the console window was:
>
> >gdb nedit
> ...
> (gdb) run -sync
> Starting program: /usr/local/bin/nedit -sync
>
> XmManager -XmAcceleratorHandler: bad news!!!
Well, this narrows it down a little. We have only 3 "bad news" warning messages
and only one of those has exactly 3 !'s, so I hope that this is an _exact_
quote. Unfortunately it is in one of those sections of code "that can't happen"
:)
> Program received signal SIGSEGV, Segmentation fault.
> 0x4019f86d in XtIsSensitive() from /usr/X11R6/lib/libXt.so.6
> (gdb)
>
> Now this looks to me as though you might be interested in my video
> setup, consisting in a cheapie Virge S3 card with 2M video RAM, using
> the S3 accelerator in X. It works okay in lots of other things
> (Netscape, StarOffice, etc). I would love to see this squashed as:
>
> 1) I reckon nedit is superb.
> 2) It is a pain in the bum using the mouse to access the menus.
>
> Jim
>
>
