From owner-freebsd-hackers Wed Jul 14 22:50:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles537.castles.com [208.214.165.101]) by hub.freebsd.org (Postfix) with ESMTP id 3F42714D12 for ; Wed, 14 Jul 1999 22:50:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA00453; Wed, 14 Jul 1999 22:45:32 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907150545.WAA00453@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Marc Tardif Cc: freebsd-hackers@freebsd.org Subject: Re: gdb instead of adb In-reply-to: Your message of "Wed, 14 Jul 1999 22:26:44 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Jul 1999 22:45:32 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is the reason why adb hasn't been ported to freebsd because the source is > proprietary? You make no sense. > 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. Note also that debugging through interrupt handlers can be problematic on PC hardware. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message