Mail Archives: djgpp/2002/01/16/14:29:37
> Date: Wed, 16 Jan 2002 12:42:03 -0600
> From: JT Williams <jeffw AT darwin DOT sfbr DOT org>
>
> Without a debug-enabled libc, `breakpoint _put_path2' in gdb
> complains that there are no line numbers for the procedure.
> Can I just compile putpath.c and include it with the object
> files when linking `less'?
Yes. But you might find out that you don't need even that: if you can
catch the call to _put_path2 that accesses the drive, all you need is
to go up the call frame stack until you get to a function in Less for
which you do have debug info. The GDB command "bt" should show the
call frame traceback, and will allow you to see where's the first
frame with debug info (it will show the source-line information).
> BTW, if I continue to single-step into _put_path, weird stuff
> happens. My keyboard get strangely remapped, and the machine
> will frequently hang (cold boot required).
What version of GDB is that? Versions before 5.0 couldn't single-step
through code which invoked __dpmi_int (if you think about it a bit,
you'll understand that entering Int 31 with the single-step,
a.k.a. TF, flag set in EFLAGS is madness ;-). GDB 5.0 does work for
me, at least in some limited testing.
- Raw text -