On the 64bit version of Haiku you actually need to build the buildtools
yourself for a complete build. The reason is that the BIOS bootloader needs
to be bult in 32bit mode, and the compiler shipped with Haiku does not
know how to do this, but the one built from the configure script can.
It does not prevent you from building other parts of Haiku.
What libraries get loaded is decided by the runtime_loader (the piece of
code that loads and runs executables). It searches for libraries according
to the LIBRARY_PATH environment variable. So if you want to use modified
libraries (built with debug symbols), you need to make sure they are in
the library path. Either change the variable, or copy the files in one
of the directories it is set to look at.
One easy way to do this is to copy the WebPositive executable somewhere,
create a "lib" directory next to it, and put the libraries you want to use
in that directory (you can use symlinks to the libraries inside Haiku
generated/
directory, so you only need to set this up once).
This works because the first entry in LIBRARY_PATH is %A/lib, and %A is a
shorthand for "the directory where the application is". Using this setup
has the advantage of not touching any other part of your Haiku install.
To build libraries in debug mode, you need to enable that in
build/jam/UserBuildConfig
Setting debug mode is normally done source directory by source directory.
For WebKit itself (which is built separately from Haiku) the process is
different, and is documented in the README in the WebKit repository.
It's the right place (the forums are also usable for this, as you prefer).
We are happy to get more help, and personally I'm particularly happy to see
more people working on the web browser.