[haiku-development] Re: Debugging tools
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sat, 12 Dec 2009 11:26:37 +0100
On 2009-12-12 at 09:11:33 [+0100], Ankur Sethi <get.me.ankur@xxxxxxxxx> wrote:
> On Sat, Dec 12, 2009 at 10:23 AM, Rahul Krishnan <pprahul@xxxxxxxxx> wrote:
> > Can someone suggest the best debugging tool, that can be used to trace the
> > different function calls, methods etc... for Haiku.
>
> GDB is included in the development tools package.
>
> > Also, is there any way to see the output of the patched code, without
> > building and creating a haiku.image everytime ?
>
> Yes. Just checkout the Haiku source tree from Haiku. You can then
> build every app separately by cd'ing into its toplevel directory in
> the source tree and running jam -q. You can do the same from Linux,
> but then you'd have to manually copy the built binary to the Haiku
> image every time.
Nah, no cd'ing and manual copying. The easiest way is use the update action
with a build profile. Like
jam -q @image update kernel
for updating the kernel on a plain Haiku raw image. For some documentation
have a look at http://www.haiku-os.org/guides, particularly the build profile
part.
CU, Ingo
Other related posts:
