RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 801775 - Unexpected error setting watchpoint
Summary: Unexpected error setting watchpoint
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gdb
Version: 7.0
Hardware: ppc64
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Jan Kratochvil
QA Contact: Miroslav Franc
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-09 13:28 UTC by Marek Polacek
Modified: 2016-02-01 02:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:58:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marek Polacek 2012-03-09 13:28:47 UTC
Description of problem:
GDB fails to continue after setting a watchpoint.

Version-Release number of selected component (if applicable):
# rpm -q gdb
gdb-7.3.50.20110722-11.el7.ppc64

How reproducible:
always

Steps to Reproduce:
# cat z.c
static int p;
int
main (void)
{
  p = 2;
  return 0;
}

# gcc z.c -g
# gdb -q ./a.out 
Reading symbols from /root/gdb/Sanity/basic-smoke-test/a.out...done.
(gdb) b main
Breakpoint 1 at 0x100004fc: file z.c, line 5.
(gdb) r
Starting program: /root/gdb/Sanity/basic-smoke-test/a.out 

Breakpoint 1, main () at z.c:5
5	  p = 2;
(gdb) watch p
Hardware watchpoint 2: p
(gdb) c
Continuing.
Unexpected error setting breakpoint or watchpoint: Invalid argument.
0x0000000010000500 in main () at z.c:5
5	  p = 2;

On x86_64 this isn't happening.

Comment 1 Jan Kratochvil 2012-03-09 13:36:13 UTC
non-x86* watchpoints are very broken now, archer-jankratochvil-watchpoint3 has been updated only for x86* but not yet for non-x86* archs.
I did not expect anyone would use it from Fedora...

Comment 2 Jan Kratochvil 2012-03-09 14:55:54 UTC
I have reproduced the problem with gdb-7.3.50.20110722-11.el7.ppc64.
I have tried to build gdb-7.4.50.20120120-29.fc17.ppc64 and it works OK.
->NOTABUG
Unaware why RHEL-7 is using so obsolete packages.

Comment 8 Ludek Smid 2014-06-13 12:58:43 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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