From owner-freebsd-hackers Wed Feb 17 0:43:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 1906510F60 for ; Wed, 17 Feb 1999 00:43:31 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id JAA27201 for ; Wed, 17 Feb 1999 09:43:30 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id JAA68932 for hackers@freebsd.org; Wed, 17 Feb 1999 09:43:29 +0100 (MET) Date: Wed, 17 Feb 1999 09:43:28 +0100 From: Eivind Eklund To: hackers@freebsd.org Subject: Re: gdb sucks - and I need to get around it. help? Message-ID: <19990217094328.C65865@bitbox.follo.net> References: <19990216170310.C60651@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990216170310.C60651@bitbox.follo.net>; from Eivind Eklund on Tue, Feb 16, 1999 at 05:03:10PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 16, 1999 at 05:03:10PM +0100, Eivind Eklund wrote: > Anybody know of any way of getting gdb to step from the start of the > program? > > I have an executable with absolutely no symbol data (symbol data is > absolutely non-available) which I *have* to get to step through, if > necessary by re-implementing gdb. Well, turns out that the behaviour / bug in question was triggered by more of gdb's weird behaviour. What was happening (which put me in the '*have* to' mode) was that top was getting segment violations due to being out of sync with the kernel, and I though that was a bad thing and should be fixed and su'ed and ran gdb on top - and got a # prompt. I have several 'role' PGP keys on this box, and a compromise would have been pretty icky. Thanks for all the suggestions - I'm sure I'll get to use them another day, as I've found this behaviour to be at least somewhat in my way time and time again. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message