Re: [Bug-gnubg] Compiling on Linux without GTK

[Jim Segrave]

On Wed 05 Mar 2003 (12:56 +0100), Holger wrote:
> At 23:20 04.03.2003 +0100, Jim Segrave wrote:
> >On Tue 04 Mar 2003 (20:49 +0100), Nis wrote:
> >> It now compiles nicely - including my additions ... can anybody tell me 
> >how
> >> to debug Segfaults?
> >
> >I've a lot of experience with this.
> ...
> >If you use emacs, then gdb is even easier to use:
> >
> >change to your gnubg source directory and start emacs
> >Esc x gdb
> >prompts with:
> >run gdb (likethis): gdb
> >enter ./gnubg <core file path>
> >eg:
> >run gdb (likethis): gdb ./gnubg /home/jes/gnubg.core
> >
> >The advantage to this is that emacs will open a source file (if it's
> >available) in one window while the debugger's in the other. The source
> >file will be positioned to the line which the debugger is on.
> 
> Seems that I'd really need to try Emacs on Windows. gdb in a DOS box (even 
> more so under Win95 because not resizeable) is a big pain in a certain 
> place.
> 
> [very good explanation about debugging snipped]
> 
> I've got a few gdb questions. I even looked through the entire gdb 
> documentation but couldn't find anything.
> 
> Is there a way to display the contents of all variables in local scope or 
> even better at the current or next source line? All globals as well? And 
> maybe even automatically?

Not that I know of.

You can use info variables to get the names of all globals (and file
scoped statics in the current file), you can then set up displays to
trak them. But I know of no way to get a list of, much less a display
of all the currently active local variables.

-- 
Jim Segrave           address@hidden