[haiku-3rdparty-dev] Re: Using the debugger
- From: "William Kocay" <wkocay@xxxxxxxxxxxxxxxx>
- To: <haiku-3rdparty-dev@xxxxxxxxxxxxx>
- Date: Fri, 6 Jun 2014 08:31:16 -0500
Hello,
I have found that the debugger works extremely well.
I compile my code using Paladin's "debug" command.
To drop into the debugger, use a statement
debugger( " some string " );
in your code.
Then you can step thru the code and set breakpoints, etc.
--William
>Hi All,
>
>I have to admit that I haven't really used the Haiku Debugger much, yet,
>but I'm working on a port now that looks like it's going to need it
>badly! Is there any documentation on it anywhere? (Aside from the blog
>posts on the website, which don't really start ftom the beginning (:-/).
>
>I can figure out a lot of it, but there are some things I think I ought
>to be able to do but can't see how to.
>
>For instance, given that I've compiled for debugging, so it can show the
>sources, I can find any source that happens to be on the stack when the
>app crashes, and set breakpoints in that area. But if I want to set a
>breakpoint in some other part of the app sources, how do I bring up that
>source?
>
>More unlikely, but nice if I could do it, if I don't have a suitably
>compiled binary, is there any cute way to match up what the debugger
>shows with the actual source? Most of the exceptions are in Haiku
>libraries (presumably because of being fed bad data), and I don't have
>debugger versions of those.
>
>Thanks,
> -- Pete --
>
Other related posts:
