Date: Sat, 24 Aug 2002 10:40:11 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: "Greg 'groggy' Lehey" <grog@FreeBSD.org> Cc: freebsd-hackers@FreeBSD.org Subject: gdbmods sript Message-ID: <15719.39627.644269.575759@grasshopper.cs.duke.edu> In-Reply-To: <20020824044646.GA87563@wantadilla.lemis.com> References: <15718.14981.573727.965999@grasshopper.cs.duke.edu> <054301c24aae$6b99ed50$b50d030a@PATRICK> <3D6642A2.3040102@agava.com> <15718.17268.289160.923598@grasshopper.cs.duke.edu> <3D664415.3040908@agava.com> <15718.17582.370143.817484@grasshopper.cs.duke.edu> <20020824044646.GA87563@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg 'groggy' Lehey writes: > > It's pretty clear at the moment that the backtrace we're talking about > is in Vinum, so the kludge in the .gdbinit file would do. On the > other hand, gdbmods looks a lot better, assuming that the "please > wait" isn't indicative of extreme slowness. The script looks quite 16 seconds to get to a gdb prompt on a 600MHz alpha.. It invokes a gdb once for each module it finds. > good; I don't suppose you have a /bin/sh version? > I don't have a /bin/sh version, I have the bad habit of doing scripts in csh... FWIW, I've cleaned up the version at http://people.freebsd.org/~gallatin/gdbmods a bit, so please refresh your copy. This fixes an infinate loop which occured if one was not using a kernel with debug symbols, and it cleans up the indenting, and silences extranious output. I don't know anything about creating ports, so I was hoping to find a ports comitter willing to make a port out of this. I think it would be quite helpful as we move towards a more modular kernel. Drew 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?15719.39627.644269.575759>