Getting build error atm on 64bit R1B4: View paste 3EXA
Not so fast. There are serious bugs remaining.
gdb-15-haiku-v11 861b4bb3113
-
Some strange illegal instruction crash that not happened before: gdb-cmds13681009269629460136.log · GitHub. Also some random SIGSEGV: gdb-cmds10242353604287662790.log · GitHub.
-
I can’t retest setting breakpoints during program running, pausing and stack trace of non-main thread because of issue 1. All this things are not working in
gdb-15-haiku-v10.
Update on 2 (tested on gdb-15-haiku-v10): setting breakpoints during program running and pausing works if running Netbeans CND branch on Haiku without using remote build host. Unable to get stack trace of non-main thread problem is still present.
1 Like
It do not work on Beta 4 and depend on recently added nightly features.
OK, then this should be set as draft at haikuports untill after R1B5 is released and running on the buildmasters.
3 Likes
Can I get the binary, source code, and build commands? This seems like an issue related to ASLR being disabled to me.
Hello,
Is it complex to update from Beta4 to nightly ?
I’m just wondering if it’s better to wait for the upcoming Beta5 to test this new GDB version.
Thanks,
Quite simple if you are OK with random crashes during boot.
Updating and downgrading your system | Haiku Project (haiku-os.org)
1 Like
Ok cool.
I have updated Haiku to nightly and launching the configure command after cloning the repo I have the below error.
Any idea how I can solve it ?
Installed gmp_devel and mpfr_devel ?
2 Likes
Ah yes thanks compilation in progress 
1 Like
I’ve successfully configured and installed gdb :
./configure --prefix=/boot/home/config/non-packaged
make
make install
However when launching gdb to check the version, it raises the below error :
@trungnt2910 any idea ?
Nuke your whole build folder, then run ./configure again after setting these environment variables:
CFLAGS="-DB_USE_POSITIVE_POSIX_ERRORS" \
CXXFLAGS="-DB_USE_POSITIVE_POSIX_ERRORS" \
./configure --whatever-other-args
For the reasons why, see this comment.
1 Like
Thanks! Working fine now
1 Like
Took a while, but I have (hopefully) cleared these bugs and the corresponding issues on GitHub.
An updated recipe has been pushed to HaikuPorts. An initial patch is currently being upstreamed (about time to ping the GDB maintainers for that).
Once again, if there are no new bug reports or reasonable feature requests I’ll consider GDB finished for the scope of this project. Hopefully I can debug a thing or two on Debugger with the little time remaining.
6 Likes
I have also successfully built and used this port of gdb. No issues so far. Although it’s early days.
However I’d like it to get to the point where you can just do pkgman install gdb and get this port. What needs to happen for that to be the case?
You can now do that. We were waiting for the HaikuPorts builders to switch to pre-beta5 packages, and today they have, so GDB is now in the depot on x86_64. (You may need to wait for today’s nightly to be able to install it, though.)
For the record, those who are still running R1B4, they need to wait also untill R1B5 is available (if they not switch to nightly (me included)) to be able to install packages buid at buildmaster atm.
2 Likes
Woot! Just in time too. I needed to enable more debugging symbols and now I doubt Debugger could load all the debugging symbols in the amount of memory I have.
My biggest complaint is it’s slow, at least on HaikuWebKit. It takes around half an hour to load debug symbols, 10 minutes to show the backtrace, and I didn’t wait long enough for it to make a breakpoint. It seems most of the time is spent looking up symbols in the object file. But I can’t reproduce that with other apps, even big ones such as Falkon. Maybe switching from dwarf-4 to dwarf-5 (the default) will help, since I expect Falkon and the rest of the apps to be compiled with dwarf-5.
2 Likes