From: Quality Quorum <qqi@world.std.com>
To: Steven Bauer <bauer@atlas.lcs.mit.edu>
Cc: <gdb@sourceware.cygnus.com>
Subject: Re: x86 hardware breakpoint question
Date: Mon, 05 Nov 2001 08:25:00 -0000 [thread overview]
Message-ID: <Pine.SGI.4.30.0111160838430.7421-100000@world.std.com> (raw)
In-Reply-To: <20011115125927.B3449@atlas.lcs.mit.edu>
On Thu, 15 Nov 2001, Steven Bauer wrote:
> Quick question, does gdb support hardware breakpoints on
> x86 architectures? I have been trying to get them to work keep
> getting an unknown error.
>
> (gdb) hbreak *0x80485d9
>
> ....
>
> warning: Cannot insert breakpoint 3:
> Error accessing memory address 0x80485d9: Unknown error 4294967295.
>
>
> One other question, is there any way to have breakpoints enabled
> when an exec occurs. What I would like to do is continue through the
> exec getting the sigtrap if the new process is loaded, delete old
> breakpoints, load the symbols for the new process, and eventually
> reset breakpoints once main is hit. The reason I want this is that
> the exec could fail, in which case I want the original breakpoints to
> still be in place. If I remove all the breakpoints before the
> exec, continue, and the exec fails, I miss all the functions I
> originally had breakpoints set for.
First, it has to be supported be stub, current stub does not do it.
Plus, there are few things to be improved on the gdb side.
>
> Thanks,
> Steve
>
>
>
>
Thanks,
Aleksey
prev parent reply other threads:[~2001-11-16 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-04 14:28 Steven Bauer
2001-11-05 6:38 ` Eli Zaretskii
2001-11-05 23:28 ` Pierre Muller
2001-11-06 12:54 ` Eli Zaretskii
2001-11-06 14:35 ` Christopher Faylor
2001-11-06 15:15 ` muller
2001-11-06 15:58 ` DJ Delorie
2001-11-06 17:12 ` muller
2001-11-06 18:13 ` DJ Delorie
2001-11-06 19:34 ` Christopher Faylor
2001-11-07 18:38 ` muller
2001-11-05 8:25 ` Quality Quorum [this message]
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=Pine.SGI.4.30.0111160838430.7421-100000@world.std.com \
--to=qqi@world.std.com \
--cc=bauer@atlas.lcs.mit.edu \
--cc=gdb@sourceware.cygnus.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