From: jtc@redback.com (J.T. Conklin)
To: gdb@sourceware.cygnus.com (GDB)
Subject: Re: breakpoint insert API (was: A patch for ia32 hardware watchpoint.)
Date: Tue, 14 Mar 2000 15:15:00 -0000 [thread overview]
Message-ID: <5mvh2p5elj.fsf@jtc.redbacknetworks.com> (raw)
In-Reply-To: <200003100128.RAA00013@alabama.wrs.com>
>>>>> "Todd" == Todd Whitesel <toddpw@windriver.com> writes:
Andrew> I'd prefer to see something that tightens rather than loosens
Andrew> access to ``struct breakpoint''. Perhaphs something along the
Andrew> lines of multi-arch where the target is notified of breakpoint
Andrew> create, insert, remove, delete operations.
Todd> Basically what I need is the moral equivalent of a "user" field
Todd> tacked onto every breakpoint struct.
Todd>
Todd> Based on my existing code, the contents of this field would be:
Todd> UINT32 breakpointID; /* WTX-supplied handle for this breakpoint */
Todd> bool is_foreign; /* true if breakpoint was set by someone else */
Todd> bool is_global; /* true if breakpoint active for all tasks */
The reason I was passing the breakpoint pointer (with the intention of
adding a "void *private_data" field), is that I don't want to preclude
any target implementation. A 32 bit integer ID is probably the most
common breakpoint handle, but you never can tell...
I don't think your is_foreign flag is suitable for the target specific
data, because it changes the behavior of generic breakpoint code. You
didn't describe is_global, so I'm not sure about it. How is it
different from (bp->thread == -1)?
--jtc
--
J.T. Conklin
RedBack Networks
WARNING: multiple messages have this Message-ID
From: jtc@redback.com (J.T. Conklin)
To: gdb@sourceware.cygnus.com (GDB)
Subject: Re: breakpoint insert API (was: A patch for ia32 hardware watchpoint.)
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <5mvh2p5elj.fsf@jtc.redbacknetworks.com> (raw)
Message-ID: <20000401000000.e2MxlAGCj4wXSQGfEmapHVHe4RZKLJymXk2mQzUR7ZU@z> (raw)
In-Reply-To: <200003100128.RAA00013@alabama.wrs.com>
>>>>> "Todd" == Todd Whitesel <toddpw@windriver.com> writes:
Andrew> I'd prefer to see something that tightens rather than loosens
Andrew> access to ``struct breakpoint''. Perhaphs something along the
Andrew> lines of multi-arch where the target is notified of breakpoint
Andrew> create, insert, remove, delete operations.
Todd> Basically what I need is the moral equivalent of a "user" field
Todd> tacked onto every breakpoint struct.
Todd>
Todd> Based on my existing code, the contents of this field would be:
Todd> UINT32 breakpointID; /* WTX-supplied handle for this breakpoint */
Todd> bool is_foreign; /* true if breakpoint was set by someone else */
Todd> bool is_global; /* true if breakpoint active for all tasks */
The reason I was passing the breakpoint pointer (with the intention of
adding a "void *private_data" field), is that I don't want to preclude
any target implementation. A 32 bit integer ID is probably the most
common breakpoint handle, but you never can tell...
I don't think your is_foreign flag is suitable for the target specific
data, because it changes the behavior of generic breakpoint code. You
didn't describe is_global, so I'm not sure about it. How is it
different from (bp->thread == -1)?
--jtc
--
J.T. Conklin
RedBack Networks
next prev parent reply other threads:[~2000-03-14 15:15 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-07 13:33 A patch for ia32 hardware watchpoint H . J . Lu
2000-03-07 21:52 ` J.T. Conklin
2000-03-08 0:46 ` Todd Whitesel
2000-03-08 6:04 ` Jim Kingdon
2000-03-08 19:44 ` Todd Whitesel
2000-04-01 0:00 ` Todd Whitesel
2000-03-09 7:06 ` Andrew Cagney
2000-04-01 0:00 ` Andrew Cagney
2000-04-01 0:00 ` Jim Kingdon
2000-03-09 5:28 ` Eli Zaretskii
2000-04-01 0:00 ` Eli Zaretskii
2000-03-09 11:28 ` breakpoint insert API (was: A patch for ia32 hardware watchpoint.) J.T. Conklin
2000-03-09 15:15 ` Jim Kingdon
2000-04-01 0:00 ` Jim Kingdon
2000-03-09 15:33 ` Andrew Cagney
2000-03-09 17:28 ` Todd Whitesel
2000-03-14 15:15 ` J.T. Conklin [this message]
2000-03-14 15:31 ` Todd Whitesel
2000-04-01 0:00 ` Todd Whitesel
2000-04-01 0:00 ` J.T. Conklin
2000-04-01 0:00 ` Todd Whitesel
2000-03-14 14:10 ` J.T. Conklin
2000-03-21 2:50 ` Andrew Cagney
2000-04-01 0:00 ` Andrew Cagney
2000-04-01 0:00 ` J.T. Conklin
2000-04-01 0:00 ` Andrew Cagney
2000-03-09 17:33 ` Todd Whitesel
2000-03-14 14:56 ` J.T. Conklin
2000-03-21 3:11 ` Andrew Cagney
2000-03-21 6:10 ` Richard Earnshaw
2000-04-01 0:00 ` Richard Earnshaw
2000-04-01 0:00 ` Andrew Cagney
2000-04-01 0:00 ` J.T. Conklin
2000-04-01 0:00 ` Todd Whitesel
2000-04-01 0:00 ` J.T. Conklin
2000-04-01 0:00 ` A patch for ia32 hardware watchpoint Todd Whitesel
2000-04-01 0:00 ` J.T. Conklin
2000-03-08 2:14 ` Eli Zaretskii
2000-04-01 0:00 ` Eli Zaretskii
2000-03-08 3:32 ` Eli Zaretskii
2000-04-01 0:00 ` Eli Zaretskii
2000-04-01 0:00 ` H . J . Lu
2000-03-13 1:50 breakpoint insert API (was: A patch for ia32 hardware watchpoint.) Stephane.Bihan
2000-03-14 14:47 ` J.T. Conklin
2000-04-01 0:00 ` J.T. Conklin
2000-04-01 0:00 ` Stephane.Bihan
2000-03-15 4:21 Stephane.Bihan
2000-03-15 7:51 ` J.T. Conklin
2000-04-01 0:00 ` J.T. Conklin
2000-04-01 0:00 ` Stephane.Bihan
2000-03-15 9:07 Stephane.Bihan
2000-04-01 0:00 ` Stephane.Bihan
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=5mvh2p5elj.fsf@jtc.redbacknetworks.com \
--to=jtc@redback.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).