From: "Eli Zaretskii" <eliz@gnu.org>
To: vinaysetty@Lucent.com
Cc: gdb@sources.redhat.com
Subject: Re: GDB for pentium III architecture
Date: Tue, 22 Feb 2005 04:35:00 -0000 [thread overview]
Message-ID: <01c51851$Blat.v2.4$357c8de0@zahav.net.il> (raw)
In-Reply-To: <6117ACCB57BFD4118C0C00508BB1B920051FC564@ii3004exch001u.in.lucent.com> (vinaysetty@Lucent.com)
> From: "Setty, Vinay J (Vinay)** CTR **" <vinaysetty@Lucent.com>
> Date: Mon, 21 Feb 2005 09:36:28 +0530
>
> Hi I am studying the gdb internals document, but lot of things are
> incomplete
Sad, but true...
> and also I wanted to know if there is any document which can give
> me the details of how gdb works on pentium III architecture. Things like
>
> * breakpointing
> * single stepping
> * signal handling
> * thread handling
> * inferior fucntion calls
> * longjumpp support
> * watchpoints etc...
x86-specific watchpoints _are_ explained in the GDB Internals manual.
See the node "Algorithms" (which also explains a bit about
breakpoints).
For other issues, I suggest to ask specific questions here.
prev parent reply other threads:[~2005-02-21 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 11:01 Setty, Vinay J (Vinay)** CTR **
2005-02-22 4:35 ` Eli Zaretskii [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='01c51851$Blat.v2.4$357c8de0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=vinaysetty@Lucent.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