Red Hat Bugzilla – Bug 163580
Command 'next' results very high CPU usage and a long time response time
Last modified: 2008-02-18 21:22:35 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5 Description of problem: I am not sure if it is a bug or a mere performance problem, but I will report it there. I am debugging a C/C++ program. I set a breakpoint (syscall open()) and run the program. When I use the 'step' command, the CPU usage is very high (almost 100%) and it takes even minutes before gdb returns to prompt state. Version-Release number of selected component (if applicable): 6.3.0.0-1.21rh How reproducible: Always Steps to Reproduce: 1. Compiles a program with -g2. 2. Start gdb with the program. 3. Set a breakpoint at a syscall, for example open. 4. Issue gdb command run. 5. When it hits the breakpoint, issue command step. Actual Results: Very high CPU usage and a very long time before gdb returns to is prompt state. Additional info:
This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks.
Fedora Core 4 is no longer maintained. Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the current Fedora release, please reopen this bug and assign it to the corresponding Fedora version.