Bug 84222 - kernel-2.4.20-2.47.1 + testsuite from gdb-5.3post-0.20021129.11 = bad juju
kernel-2.4.20-2.47.1 + testsuite from gdb-5.3post-0.20021129.11 = bad juju
Status: CLOSED DUPLICATE of bug 84220
Product: Red Hat Linux
Classification: Retired
Component: gdb (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Elena Zannoni
Brian Brock
:
Depends On:
Blocks: 79578
  Show dependency treegraph
 
Reported: 2003-02-13 12:21 EST by Tim Powers
Modified: 2008-01-17 12:49 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tim Powers 2003-02-13 12:21:52 EST
The gdb-5.3post-0.20021129.11 build spawns an attach1 process in the
testsuite and it renders build machines and mass rebuild test machines unusable.
The running kernel on the machine in question is kernel-2.4.20-2.47.1 (msw says
the test suite does not behave this way with kernel-2.4.20-2.26, and that
problem shows on 2.4.20-2.29 as well). Here are the details:

[root@loki root]# ps auxwww | grep attach
#500      2927 88.8  0.0  1480  244 ?        R    02:11 658:33 /tmp/attach1.20553
[root@loki root]# cd /proc/2927
[root@loki 2927]# ls -l
total 0
-r--r--r--    1 500      500             0 Feb 12 14:33 cmdline
-r--r--r--    1 500      500             0 Feb 12 14:33 cpu
lrwxrwxrwx    1 500      500             0 Feb 12 14:33 cwd ->
/mnt/build/rebuildtest/rebuild/pkgs/gdb/build-i386-redhat-linux-gnu/gdb/testsuite
(deleted)
-r--------    1 500      500             0 Feb 12 14:33 environ
lrwxrwxrwx    1 500      500             0 Feb 12 14:33 exe ->
/mnt/build/rebuildtest/tmp/attach1.20553 (deleted)
dr-x------    2 500      500             0 Feb 12 14:33 fd
-r--r--r--    1 500      500             0 Feb 12 14:33 maps
-rw-------    1 500      500             0 Feb 12 14:33 mem
-r--r--r--    1 500      500             0 Feb 12 14:33 mounts
lrwxrwxrwx    1 500      500             0 Feb 12 14:33 root ->
/mnt/build/rebuildtest
-r--r--r--    1 500      500             0 Feb 12 14:33 stat
-r--r--r--    1 500      500             0 Feb 12 14:33 statm
-r--r--r--    1 500      500             0 Feb 12 14:33 status
Comment 1 Ingo Molnar 2003-02-13 12:34:56 EST
please "kill -8 PID" the runaway process and look at the backtrace in
"gdb -c core.PID", does that help?

("ulimit -c 1000000" as well, default coredump size might be 0)
Comment 2 Tim Powers 2003-02-13 13:41:26 EST
It's going to take a while to do this on the machine I saw the problem on
(there's a lot happening on that machine right now), but I'm trying. Just
starting the rebuild of the package is taking a very long time.

If you want to reproduce this just try rebuilding the gdb-5.3post-0.20021129.11
package on a machine which is running 2.4.20-2.47.1. 
Comment 3 Ingo Molnar 2003-02-13 13:51:17 EST
do this on perf53 to reproduce the failure (as root, in the /root directory):


# /tmp/attach2.1414 &
[1] 14152
# gdb
(gdb) attach 14152
(gdb) s should_exit=1
Program received signal SIGSTOP, Stopped (signal).

sometimes a 'c' has to be done, and the bogus SIGSTOP message is displayed then.
This is clearly a SIGCONT/SIGSTOP or ptrace bogosity.
Comment 6 Elena Zannoni 2003-02-13 18:23:51 EST
I did already create a gdb bug for this. 84220.

I disabled the tests in the gdb-5.3post-0.20021129.12 build, so this shouldn't
affect you guys any more.

It is gdb's fault that it doesn't clean after itself if something goes wrong
during the test. The reason that this didn't happen with older kernels (pre
NPTL) is that now there is an extra SIGSTOP after attaching to a process, and
gdb doesn't handle that properly. This screws up the whole test sequence.

So I am going to close this. OK?
Comment 9 Matt Wilson 2003-02-14 00:44:09 EST

*** This bug has been marked as a duplicate of 84220 ***
Comment 10 Red Hat Bugzilla 2006-02-21 13:51:46 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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