Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!ames!cronkite.cisco.com!cisco.com!vandys From: vandys@cisco.com (Andrew Valencia) Newsgroups: comp.unix.bsd Subject: Re: Source level kernel debugger for HP-UX Date: 11 Jul 94 15:25:31 GMT Organization: cisco Systems Lines: 24 Message-ID: <vandys.773940331@cisco.com> References: <2vqe7v$go7@tribune.usask.ca> NNTP-Posting-Host: glare.cisco.com Keywords: debug, kernel, HP-UX In <2vqe7v$go7@tribune.usask.ca> vineet@sparkle.usask.ca (Vineet Chikarmane) writes: >I need something that will let me do source-level debugging of >the kernel in execution. Are there any of those thingies that >let you boot and debug a kernel on one machine while the debugger >itself runs on another? Well, 300's (last time I hacked on the stuff) have SYSDEBUG, which will show up on your boot menu. This is a kinda-sorta source level debugger, although mostly it's a symbolic assembly code debugger. As I recollect, you could compile in -g information for a *limited* number of modules, using some strange trick having to do with a magic filename. It would then cite source line number (although not show the source--you had to have another machine for viewing the source). In practice, we all lived with the symbolic assembly, which isn't too bad. The kernel debugger worked even before mapping was enabled. I used it to port a VM system, so this was handy! :-) This is all I remember, and I hack on 300's no more. At least now you know what to beg out of HP. Regards, Andy