Re: Info from GDB?

On 2005-08-23 at 13:58:29 [+0200], Andrew McCall wrote:
> Axel Dörfler wrote:
> > Andrew McCall <[email protected]> wrote:
> > 
> >>When your dropped to the GDB in Haiku, what (and how do I get it!)
> >>information from GDB do developers want submitting to the bug
> >>database?
> > 
> > As long as you don't use gdb remotely, you are always debugging a user
> > application, so this list might not be appropriate here.
> > But anyway, I think what you're asking is how to get the stack crawl
> > (sc) you usually sent to a developer? In gdb it's called back trace and
> > it can be printed out using the "bt" command.
> > Did I understand your question correctly?
> 
> Yes, you understood :)  I did end up doing bt, but it didn't produce as
> much info as Be's sc did.

There are other commands to get more info (registers etc.), but I don't have 
the reference at hand right now. "help" shows a command category listing. 
And "help <category>" gives you the available commands in the category.

> Thinking about it, its the Deskbar that caused the drop to gdb.  For
> some reason I recalled that BeOS used to only drop to the kdl when there
> was a kernel panic, I wrongly presumed the same of Haiku, and if I had
> actually thought twice about what was in front of me I would have
> realised it.

Although it looks similar, dropping into gdb is not KDL. KDL means the 
kernel encountered a serious problem and the system is stopped while being 
in KDL. Dropping directly into gdb (that is without getting the "The app ... 
encountered a problem that prevents it from continuing..." alert, where you 
can choose "Debug") means, that the app server crashed. It's a built in 
special case that allows at least some debugging, while you would otherwise 
only see a frozen screen.

CU, Ingo


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf