From: James Cownie <jcownie@etnus.com>
To: gdb@sources.redhat.com
Subject: Re: gdb doesn't work very well with dynamic linked binaries
Date: Wed, 06 Sep 2000 03:54:00 -0000 [thread overview]
Message-ID: <200009061054.GAA28894@albacore> (raw)
This threads seems really to have morphed to be about using the
hardware watchpoint registers on IA32.
So :-
Note that there are a couple of linux kernel bugs in 2.2 (one of which
was fixed in 2.2.17) which affect the use of the debug registers.
The first bug (which was fixed in 2.2.17) was that the debug status
register wasn't being saved where it could be seen by ptrace, so if
you were relying on looking at the hardware status register you were
stuffed.
The second (which isn't yet fixed) I described with a test case in a
previous mail here. ( http://sources.redhat.com/ml/gdb/2000-08/msg00072.html )
Basically the kernel ignores all hardware
watchpoints from the point where one of them is triggered inside the
kernel until a reschedule. This means many watchpoints at user level
can be silently skipped :-(
AFAICS both bugs remain in 2.4.0-test7.
-- Jim
James Cownie <jcownie@etnus.com>
Etnus, LLC. +44 117 9071438
http://www.etnus.com
--
-- Jim
James Cownie
jcownie@etnus.com
Etnus, Inc.
Phone +44 117 9071438
next reply other threads:[~2000-09-06 3:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-06 3:54 James Cownie [this message]
2000-09-06 4:58 ` Mark Kettenis
-- strict thread matches above, loose matches on Subject: below --
2000-09-07 3:27 James Cownie
2000-09-07 1:55 James Cownie
2000-09-07 3:09 ` Mark Kettenis
2000-09-07 8:02 ` Eli Zaretskii
2000-09-08 8:30 ` Mark Kettenis
2000-09-09 14:39 ` Peter.Schauer
[not found] <20000901192328.A28312@valinux.com>
[not found] ` <200009041047.LAA10659@phal.cygnus.co.uk>
2000-09-04 8:49 ` H . J . Lu
2000-09-04 10:52 ` Mark Kettenis
2000-09-04 11:11 ` Daniel Berlin
2000-09-04 11:22 ` Ulrich Drepper
[not found] ` <drepper@redhat.com>
2000-09-05 19:12 ` Kevin Buettner
2000-09-04 16:45 ` H . J . Lu
2000-09-04 22:49 ` Eli Zaretskii
2000-09-04 23:32 ` H . J . Lu
2000-09-05 3:36 ` Eli Zaretskii
2000-09-05 6:34 ` Mark Kettenis
2000-09-05 8:47 ` Eli Zaretskii
2000-09-05 17:06 ` Mark Kettenis
2000-09-05 22:52 ` Eli Zaretskii
2000-09-05 8:49 ` H . J . Lu
2000-09-05 18:23 ` Stan Shebs
2000-09-05 18:33 ` H . J . Lu
2000-09-05 22:54 ` Eli Zaretskii
2000-09-05 8:44 ` H . J . Lu
2000-09-05 18:02 ` Stan Shebs
2000-09-05 20:45 ` H . J . Lu
2000-09-05 22:55 ` Eli Zaretskii
2000-10-14 23:09 ` Andrew Cagney
2000-09-05 22:53 ` Eli Zaretskii
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=200009061054.GAA28894@albacore \
--to=jcownie@etnus.com \
--cc=gdb@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).