X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f Date: Wed, 16 Jan 2002 21:22:49 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: jeffw AT darwin DOT sfbr DOT org Message-Id: <6480-Wed16Jan2002212249+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9 CC: djgpp AT delorie DOT com In-reply-to: <20020116124203.B14634@kendall.sfbr.org> (message from JT Williams on Wed, 16 Jan 2002 12:42:03 -0600) Subject: Re: less probed my zip References: <20020107092245 DOT A22916 AT kendall DOT sfbr DOT org> <20020107093742 DOT B22916 AT kendall DOT sfbr DOT org> <6480-Mon07Jan2002233835+0200-eliz AT is DOT elta DOT co DOT il> <20020116124203 DOT B14634 AT kendall DOT sfbr DOT org> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Wed, 16 Jan 2002 12:42:03 -0600 > From: JT Williams > > 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.