From: Craig Rodrigues <rodrigc@mediaone.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: gdb hardware breakpoints under Linux PPC?
Date: Sat, 21 Apr 2001 16:51:21 -0400 [thread overview]
Message-ID: <20010421165121.B7985@mediaone.net> (raw)
Hello,
I am debugging a problem with an application that
works under x86 based Redhat Linux 6.2, but
suffers a bizarre memory corruption under LinuxPPC 2000-Q4.
I am using gdb version 5 (gdb 5.05 rpm that comes with LinuxPPC).
I would like to set a hardware watchpoint under gdb
on a certain region of memory, to see why it is getting
clobbered (the element getting clobbered under PPC is
a dynamically allocated structure in a linked list). Does
gdb 5 support hardware watchpoints under Linux PPC?
Can someone give me an example of how to set a watchpoint?
The gdb manual is a bit vague in explaining this.
Thanks.
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@mediaone.net
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-04-21 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-21 20:51 Craig Rodrigues [this message]
2001-04-22 2:23 ` gdb hardware breakpoints under Linux PPC? Kevin Buettner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010421165121.B7985@mediaone.net \
--to=rodrigc@mediaone.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).