Bug 40936 - Disable hardware watchpoint locks up machine.
Disable hardware watchpoint locks up machine.
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: gdb (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-05-16 13:45 EDT by hjl
Modified: 2007-04-18 12:33 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-05-16 17:30:31 EDT
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 hjl 2001-05-16 13:45:19 EDT
When I disable a hardware watchpoint,  my SMP machine will lockup hard
when I start another gdb session.
Comment 1 Trond Eivind Glomsrxd 2001-05-16 14:09:13 EDT
Could you give an example? (and please try the new gdb version (5.0rh-9 or
higher) at http://people.redhat.com/teg/gdb/ )
Comment 2 hjl 2001-05-16 17:13:55 EDT
The new gdb does the same.

# cat gdb.c
int x = 0;

foo ()
{
  x = 1;
}

bar ()
{
  x = 2;
}

main ()
{
  foo ();
  bar ();
}

# gcc -g gdb.c 
# gdb a.out
(gdb) watch x
(gdb) r
Starting program: /home/hjl/tmp/a.out 
Hardware watchpoint 1: x
Hardware watchpoint 1: x
Hardware watchpoint 1: x

Old value = 0
New value = 1
foo () at gdb.c:6
6       }
(gdb) c
Continuing.
Hardware watchpoint 1: x

Old value = 1
New value = 2
bar () at gdb.c:11
11      }(gdb) c
Continuing.

Program exited with code 01.
(gdb) dis 1
(gdb) r
Starting program: /home/hjl/tmp/a.out 

My SMP machine locks up at this point. It works fine on UP machine. It may be
a kernel bug. Can you try that on your SMP machine?

Comment 3 Trond Eivind Glomsrxd 2001-05-16 17:30:25 EDT
Doesn't happen on my machine... I'll try another later.
Comment 4 Trond Eivind Glomsrxd 2001-05-16 17:45:01 EDT
I've tried it on another SMP machine, this time with our standard kernel: It
doesn't crash there either...

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