gdb on ppc often remains stuck in call___do_global_ctors_aux
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cell GCC |
Fix Released
|
High
|
Unassigned | ||
gdb (Debian) |
New
|
Unknown
|
|||
gdb (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I've a ppc64 machine (an iMac G5). Whenever I try to run gdb on a program, after having installed its dbgsym package, stepping with next causes sooner or later the output of the message:
"Single stepping until exit from function call___
If I try to use "step" instead of "next", cpu goes to 100% and I've to SIGINT the debugged program. This makes virtually impossible to debug something, if you don't want to set a breakpoint every other line and use "continue" to reach it.
Also other people seem to have hit this bug, in Debian:
http://<email address hidden>
Or also:
http://
I don't know if this can be related:
https:/
Unfortunately I'm quite in a hurry now.
---------- Example session: -----------
matteo@
[...]
Using host libthread_db library "/lib/libthread
(gdb) break main
Breakpoint 1 at 0x1000618c: file daemon/main.c, line 316.
(gdb) r
Starting program: /usr/bin/pulseaudio
[Thread debugging using libthread_db enabled]
[New Thread -134462368 (LWP 17533)]
[Switching to Thread -134462368 (LWP 17533)]
Breakpoint 1, main (argc=1, argv=0xffec8784) at daemon/main.c:316
warning: Source file is more recent than executable.
316
(gdb) n
329 struct timeval tv;
(gdb)
315 pa_mainloop *mainloop = NULL;
(gdb)
308 }
(gdb)
329 struct timeval tv;
(gdb)
308 }
(gdb)
315 pa_mainloop *mainloop = NULL;
(gdb)
316
(gdb)
321 int valid_pid_file = 0;
(gdb)
329 struct timeval tv;
(gdb)
0x10007a80 in call___
(gdb)
Single stepping until exit from function call___
which has no line number information.
0xf7ff4cc4 in ?? () from /lib/ld.so.1
(gdb)
Cannot find bounds of current function
(gdb)
Cannot find bounds of current function
Related branches
CVE References
Changed in gdb: | |
status: | Unknown → Fix Released |
Changed in gdb: | |
status: | Fix Released → New |
Changed in ubuntu-ps3-port: | |
importance: | Undecided → High |
milestone: | none → ubuntu-9.04 |
status: | New → Confirmed |
Changed in ubuntu-ps3-port: | |
status: | Incomplete → Fix Released |
affects: | ubuntu-ps3-port → cell-gcc |
Changed in cell-gcc: | |
milestone: | ubuntu-9.04 → none |
Isn't anyone else experiencing this bug? I still can't use gdb on my PPC machine. Fortunately it isn't my main development platform, but I consider this bug a major problem nonetheless, which needs fixing.