Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@wins.uva.nl>
To: jtc@redback.com
Cc: eliz@is.elta.co.il, kevinb@cygnus.com, gdb@sources.redhat.com
Subject: Re: [RFC] Unified watchpoints for x86 platforms
Date: Fri, 16 Feb 2001 00:00:00 -0000	[thread overview]
Message-ID: <200102160800.f1G80Gv00277@delius.kettenis.local> (raw)
In-Reply-To: <5melwzd0qr.fsf@jtc.redback.com>

   From: jtc@redback.com (J.T. Conklin)
   Date: 15 Feb 2001 14:45:16 -0800

   >>>>> "Eli" == Eli Zaretskii <eliz@delorie.com> writes:
   >> > Is there any particular reason why you need the PID argument?  AFAICS
   >> > it will always be equal to INFERIOR_PID, so I think we can do without
   >> > it.  This is also true for the other i386_hwbp_* functions you're
   >> > proposing.
   >> 
   >> I think it'd be better to not rely on ``inferior_pid''.  I would
   >> rather see the explicitly passed.  There will come a day when GDB
   >> is able to debug more than one process at a time and to perpetuate
   >> reliance on inferior pid would be short sighted.

   Eli> I have two opposite opinions here.  We need to resolve this somehow.

   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.  It is not clear to me that adding such an
   argument "because it will be needed" is correct, considering that the
   design has not yet started.  The truth is we don't know "what" will be
   needed, so we'll have to revisit this function (among many others)
   down the line anyway.

I agree with J.T. here.

Mark


  parent reply	other threads:[~2001-02-16  0:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200009070855.EAA00749@albacore>
     [not found] ` <200009071500.LAA07756@indy.delorie.com>
     [not found]   ` <200009081529.e88FTjx15960@debye.wins.uva.nl>
2001-02-10  7:34     ` 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
     [not found]                   ` <eliz@delorie.com>
2001-02-16  0:45                     ` Kevin Buettner
2001-02-16 10:52                   ` J.T. Conklin
2001-02-16  0:00                 ` Mark Kettenis [this message]
2001-02-15  9:08         ` H . J . Lu

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=200102160800.f1G80Gv00277@delius.kettenis.local \
    --to=kettenis@wins.uva.nl \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=jtc@redback.com \
    --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