Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 163580 - Command 'next' results very high CPU usage and a long time response time
Summary: Command 'next' results very high CPU usage and a long time response time
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-07-19 06:23 UTC by Neo
Modified: 2008-02-19 02:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-02-19 02:22:35 UTC

Attachments (Terms of Use)

Description Neo 2005-07-19 06:23:24 UTC
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):

How reproducible:

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:

Comment 1 Christian Iseli 2007-01-20 00:27:32 UTC
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 ?


Comment 2 petrosyan 2008-02-19 02:22:35 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.