This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb eats 100% cpu for relative long time when I single step one instruction
Hello,
> These are just display panes. It sounds like something is broken
> inside the TUI. You'll have to build a debuggable GDB and attach
> another gdb to it to see what it's spinning on.
I made a screenshot[1]. I guess that every time I do a single step gdb
tries to analyze the jzero_far function he thinks I am in. He also says
jzero_far+1846439. But if this doesn't help I can attach.
I executed 'ni' in the gdb window and attached
strace -o dbg -fp `pidof gdb`
And he does:
(excalibur) [~] cat dbg
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0x8249d14, [0x49e94050]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0xb7fd0ce0, [0xb74400c0]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0x8249d14, [0x49e94050]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0x8249d18, [0x90fffffd]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0xb7fd0ce0, [0xb74400c0]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0x8249d18, [0x90fffffd]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0xb7fd0ce0, [0xb74400c0]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0x8249d1c, [0xff08458b]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0xb7fd0ce0, [0xb74400c0]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0x8249d1c, [0xff08458b]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0xb7fd0ce0, [0xb74400c0]) = 0
1317 ptrace(PTRACE_PEEKTEXT, 1318, 0x8249d1c, [0xff08458b]) = 0
...
(excalibur) [~] wc -l dbg
1728579 dbg
And I started the ptrace *after* I typed 'ni' in and interrupted it before 'ni'
came back:
Thomas
[1] gdb screenshot
http://wwwcip.informatik.uni-erlangen.de/~sithglan/shot1.png