This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/19598] GDB breakpoint locks up Ubuntu UI, requiring reboot
- From: "drn at nadler dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 13 Feb 2016 16:33:13 +0000
- Subject: [Bug breakpoints/19598] GDB breakpoint locks up Ubuntu UI, requiring reboot
- Auto-submitted: auto-generated
- References: <bug-19598-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19598
--- Comment #10 from Dave Nadler <drn at nadler dot com> ---
OK, I managed to run the application from a non-GUI window with GDB, and found:
- when GDB breaks, the GUI is locked up, and
- if I "continue" in GDB, the GUI resumes normal operation
Leaves the question:
1) Most important: How can I prevent what-ever lockup is occurring on a GDB
breakpoint? This is really impeding work on this particular project; its
enormously easier and more productive to work in Eclipse than with raw GDB...
2) Why did debugging with this exact breakpoint work a few months ago? There's
been to my knowledge no change in the application structure (for example grab
functions etc)...
Thanks again for the help,
Best Regards, Dave
=== Running with GDB in non-GUI window (Ctrl-Alt-F1) ===
export DISPLAY=:0
gdb tophat/output/UNIX_TEST/bin/tophat
break InputEvents::eventDRNtestHook
run -800x600
--
You are receiving this mail because:
You are on the CC list for the bug.