Date: Thu, 15 Jul 1999 23:38:37 +0930 From: Greg Lehey <grog@lemis.com> To: Mike Smith <mike@smith.net.au>, Marc Tardif <intmktg@CAM.ORG> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gdb instead of adb Message-ID: <19990715233837.17211@mojave.lemis.com> In-Reply-To: <199907150545.WAA00453@dingo.cdrom.com>; from Mike Smith on Wed, Jul 14, 1999 at 10:45:32PM -0700 References: <Pine.SOL.4.10.9907142220080.17292-100000@Stratus.CAM.ORG> <199907150545.WAA00453@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 14 July 1999 at 22:45:32 -0700, Mike Smith wrote: >> Is the reason why adb hasn't been ported to freebsd because the source is >> proprietary? > > You make no sense. What don't you understand? It makes plenty of sense to me (and the answer is: yes). >> If gdb should suffice for my debugging needs, how can a breakpoint be set >> at a particular interrupt, or even at any interrupt? The break command >> only seems to accept functions, offsets, linenumbers and addresses... >> I'm all out of ideas and the gdb info file isn't helping. > > You make little more sense, unless you are talking about using > gdb-remote on a running kernel, in which case you should know that > interrupts are vectored through functions, and thus the entire issue is > moot. Translation: to set a breakpoint on an "interrupt", set the breakpoint on its interrupt handler. > Note also that debugging through interrupt handlers can be > problematic on PC hardware. On all hardware. But if Marc has used adb to set breakpoints on interrupt handlers, he'll know that. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990715233837.17211>