Red Hat Bugzilla – Bug 103055
kernel problem with gdb on uniprocessor machines
Last modified: 2007-11-30 17:06:57 EST
Description of problem:
I see the gdb testsuite results change with two different versions of the same
kernel, same nightly build. The only difference I can see is that one machine is
SMP and the other is not.
Have a look at the test results for gdb-any on x86 in
The following run has Linux 2.4.21-1.1931.2.399.entsmp and produces 31 failures:
This one instead has Linux 2.4.21-1.1931.2.399.ent and produces 58 failures.
They are from the same nightly build, the only different thing is the kernel.
The new failures are thread related, in gdb.threads/schedlock.exp.
The inferior program runs away, like this, the other failures are cascade
failures from this one problem.
42 (*myp) ++;
(gdb) PASS: gdb.threads/schedlock.exp: step to increment (unlocked 6)
Program exited normally.
The program is not being run.
(gdb) FAIL: gdb.threads/schedlock.exp: step to increment (unlocked 7)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Roland's lost request:
------- Additional Comments From email@example.com 2003-09-30 16:42 -------
This could be a userland bug triggered by timing differences rather than a
kernel bug. We need to see at low level what is going wrong. Have you
reproduced this problem by hand, outside the STP framework? Have you tried the
failing gdb run under strace to watch its ptrace calls?
This is an ancient bug. Can the problem still be reproduced on RHEL3 U6?
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.