From: jtc@redback.com (J.T. Conklin)
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: kevinb@cygnus.com, kettenis@wins.uva.nl, gdb@sources.redhat.com
Subject: Re: [RFC] Unified watchpoints for x86 platforms
Date: Fri, 16 Feb 2001 10:52:00 -0000 [thread overview]
Message-ID: <5m7l2qbgv0.fsf@jtc.redback.com> (raw)
In-Reply-To: <200102160729.CAA01185@indy.delorie.com>
>>>>> "Eli" == Eli Zaretskii <eliz@delorie.com> writes:
>> From: jtc@redback.com (J.T. Conklin)
>> Date: 15 Feb 2001 14:45:16 -0800
>>
>> We're going to need to pass a PID, or perhaps some new representation
>> of a execution context, to a lot of code functions that don't allready
>> have such an argument.
Eli> Sorry, I'm not sure I'm following: why do you envision we'll need to
Eli> pass the PID to functions that don't receive it today? What
Eli> function(s) did you have in mind?
I was speaking in generalities.
But if GDB is ever going to be able to debug multiple independent
processes (perhaps with multiple threads) as has been a stated long
term goal, we are going to have to entirely revamp how a "execution
context" is represented, and how target functions know what context
they are operating on. IMO, an inferior_pid global, and passing pids
to various functions is not enough.
--jtc
--
J.T. Conklin
RedBack Networks
next prev parent reply other threads:[~2001-02-16 10:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-07 1:55 gdb doesn't work very well with dynamic linked binaries James Cownie
2000-09-07 3:09 ` Mark Kettenis
2000-09-07 8:02 ` Eli Zaretskii
2000-09-08 8:30 ` Mark Kettenis
2001-02-10 7:34 ` [RFC] Unified watchpoints for x86 platforms Eli Zaretskii
2001-02-10 10:19 ` H . J . Lu
2001-02-10 11:28 ` Eli Zaretskii
2001-02-15 3:48 ` Eli Zaretskii
2001-02-15 8:17 ` Mark Kettenis
2001-02-15 9:32 ` Eli Zaretskii
2001-02-15 10:33 ` Mark Kettenis
2001-02-15 13:26 ` Eli Zaretskii
2001-02-15 10:41 ` Kevin Buettner
2001-02-15 13:26 ` Eli Zaretskii
2001-02-15 14:46 ` J.T. Conklin
2001-02-15 16:11 ` Kevin Buettner
2001-02-15 23:29 ` Eli Zaretskii
2001-02-24 10:14 ` Eli Zaretskii
2001-02-27 3:28 ` Mark Kettenis
2001-02-27 10:57 ` Eli Zaretskii
2001-03-21 15:59 ` [RFA] " Eli Zaretskii
2001-02-15 23:30 ` [RFC] " Eli Zaretskii
2001-02-16 10:52 ` J.T. Conklin [this message]
2001-02-16 0:00 ` Mark Kettenis
2001-02-15 9:08 ` H . J . Lu
2000-09-09 14:39 ` gdb doesn't work very well with dynamic linked binaries Peter.Schauer
-- strict thread matches above, loose matches on Subject: below --
2000-06-02 8:40 Proposal: convert function definitions to prototyped form David Taylor
2000-06-02 12:10 ` Kevin Buettner
2000-06-03 3:58 ` Eli Zaretskii
[not found] ` <eliz@delorie.com>
2000-06-03 10:50 ` Kevin Buettner
2000-06-03 11:37 ` Eli Zaretskii
2000-06-03 18:18 ` Andrew Cagney
2000-06-03 15:42 ` Kevin Buettner
2001-02-16 0:45 ` [RFC] Unified watchpoints for x86 platforms 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=5m7l2qbgv0.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
--cc=kevinb@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).