Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

gdb-dashboard unresponsive upon receiving SIGSEGV on binary being debugged

See original GitHub issue

Using the Godot Game Engine at commit 4abebfa476c54552f55b03bb43d72bd29a7a26b1

git clone https://github.com/godotengine/godot
cd godot
git checkout 4abebfa476c54552f55b03bb43d72bd29a7a26b1
scons platform=x11 CCFLAGS='-D_FORTIFY_SOURCE=2' CXX=g++ target=release_debug debug_release=yes debug_symbols=full tools=yes bits=64 -j$(nproc)

And opening the following project which causes a crash: xml-multiline-comment.zip

unzip xml-multiline-comment.zip
cd xml-multiline-comment
gdb /path/to/godot.x11.opt.tools.64 # it's a stack smash -- may have to run several time to trigger the crash

Makes gdb-dashboard unresponsive for a good while. Doesn’t seem related to #208, but could be.

Issue Analytics

State:
Created 3 years ago
Comments:13 (8 by maintainers)

Top GitHub Comments

1reaction

Rubonnekcommented, Jul 17, 2020

Yeah, it’s kinda hackish and not optimal at all.

Thank you again for gdb-dashboard – I wasn’t aware the gdb module API could be such a nightmare on these cases.

1reaction

Rubonnekcommented, Jul 16, 2020

Wow, I’ve never seen anything like that before.

And by the way, thank you so much for gdb-dashboard – it really makes gdb much easier to use.

Top Results From Across the Web

SIGSEGV when run a program in gdb · Issue #278 · copy/v86

I want to debug my program with gdb on v86. ... my program to gdb and started, I got "Program received signal SIGSEGV,...

gdb - identify the reason of the segmentation fault

This message indicates that there is a segfault at instruction pointer 80e6433 and stack pointer f2afd4e0. Looks that the program tries to read/ ......

getaddrinfo causes segfault if multithreaded and linked statically

The getaddrinfo call causes an internal segmentation fault when called from threads and the binary is linked with "-static".

gdb crashes when trying to start a debugging session

So without the debug symbols installed, gdb inserts the ARM breakpoint instruction sequence for the dynamic loader probes, when it should be ...

DDD use - GNU.org

to run DDD with JDB, PYDB, Perl, or Bash as an inferior debugger. If the program is an executable binary, you should use...