> JV> Segmentation fault.  Which brings us to debugging these things under
> JV> Linux...  How is it done?  
> 
> While you're in gdb you should ( assuming things are working correctly)
> be able to do most debugging type things other than actually running the
> program.  E.g. looking at the values of variables and such.
It's not as intuitive as Turbo Debugger, that's a fact. Even with the ugly
info pages converted to HTML, things are still a tad confusing. I was
hoping to get a simple answer, like "press B" or something, and have it
load the source into an editor with a big arrow pointing at the bug. A
hardcopy book on gdb would be great- the help screen is my only savior at
this point.
What I get with 'gdb sat' is a message "No debugging symbols found"
I'm using gcc -E to preprocess sat.S into sat.s for the assembler,
then linking the object file with gcc. What happened to the symbols?
	gcc -E sat.S -o sat.s
	as sat.s -o sat.o
	gcc sat.o -o sat -lncurses
Running the program under gdb produces a few complaints about the lack
of symbols, then
                        Segfault
                        0x4006bf7e in vfprintf ()
and since nowhere do I find a call to vfprintf in Jan's code, this info
is fairly useless to me.  :(
 
> The video you use shouldn't really make much difference - gdb is
> strictly text mode in any case.
I meant that my Hercules mono is probably causing some problems with Jan's
code, not the debugger (ncurses.asm, I suspect). ncurses~terminfo has been
hard at work causing me fits elsewhere.. 
Lessee, AT&T syntax code commented in Dutch. The gdb debugger even makes
D86 look good..  Yup, I'm in trouble.  ;-)
--- ifmail-tx (i386 Linux)
---------------