Date: Thu, 8 Apr 1999 18:29:41 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: paul@originative.co.uk Cc: simokawa@sat.t.u-tokyo.ac.jp, dfr@nlsystems.com, freebsd-alpha@FreeBSD.ORG Subject: RE: _start or __start? Message-ID: <14093.11304.145065.519608@grasshopper.cs.duke.edu> In-Reply-To: <A6D02246E1ABD2119F5200C0F0303D10FEA6@octopus> References: <A6D02246E1ABD2119F5200C0F0303D10FEA6@octopus>
next in thread | previous in thread | raw e-mail | index | archive | help
paul@originative.co.uk writes: > > Darn! I'd forgotten about this.. My gdb only works interactively for > > user programs. > > > > As to where the problem is, I have no clue. That's why I never fixed > > it. > > Ahh, that explains why I couldn't use it to do postmortem analysis then! You can't use it for postmortem analysis of user programs, but it *should* work for postmortem analysis of kernel crashdumps. The code that writes these two types of core files is totally different. I've had problems getting a proper stack trace out if it (sometimes it works, sometimes it doesn't, and I'm not good enough at hacking gdb to know how to fix it or even what's wrong), but you should be able to get a valid crashdump and at least look at global variables. In the worst case, you should at least be able to get a trace with ddb on the way down. I'm eagerly looking forward to somebody with a clue getting gdb working on alphas... Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14093.11304.145065.519608>