Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Mircea Gherzan'" <mircea.gherzan@intel.com>,
	       "'Pedro Alves'"	<palves@redhat.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>,
	       "'mgherzan@gmail.com'" <mgherzan@gmail.com>
Subject: RE: [PATCH] Add the -catch-load and -catch-unload MI commands.
Date: Mon, 10 Sep 2012 15:04:00 -0000	[thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC5E118AA286@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <504DFDB8.7090005@intel.com>

> -----Original Message-----
> From: Mircea Gherzan [mailto:mircea.gherzan@intel.com] 
> Sent: Monday, September 10, 2012 10:48 AM
> To: Pedro Alves
> Cc: Marc Khouzam; 'gdb-patches@sourceware.org'; 'mgherzan@gmail.com'
> Subject: Re: [PATCH] Add the -catch-load and -catch-unload MI 
> commands.
> 
> Hi,
> 
> Thank you for your feedback.
> 
> On 10.09.2012 16:09, Pedro Alves wrote:
>  > [...]
> > I don't this would be a good idea compared to separate 
> commands.  Each
> > of those catch variants takes different parameters/options.  I'm not
> > seeing what putting them all under the same roof would buy.
> 
> I am still in favour of having them as separate commands, but, if the 
> powers that be decide otherwise, I am willing to rework the patch.
> 
> > In the CLI, although "catch exec", "catch fork", "catch 
> syscall", etc.
> > have the same prefix, they're really implemented as 
> separate commands
> > as well.
> >
> 
> Please let me know if there are any issues that prevent this 
> patch from getting merged.

An enhancement that would be nice (but may not be blocking) is
to support a '-d' flag like -break-insert does.  This would
create the catchpoint in a disabled state.

Currently, a frontend that wants to create a disabled catchpoint
must do:
 catch load
 -break-disabled 1 (assuming the catchpoint number is 1)

in non-stop mode, this can cause a race condition where the 
catchpoint could hit before it is disabled.  It would be better 
to do a single command:
  -catch-load -d

Note that I've never actually seen this happen, but I believe
the risk is there.

BTW, we have the same potential problem with watchpoints 
which use -break-watch.

Thanks for these proposed new MI commands, they will be useful
for Eclipse.

Marc



> 
> Thanks,
> Mircea
> 
> -- 
> 
> Intel GmbH
> Dornacher Strasse 1
> 85622 Feldkirchen/Muenchen, Deutschland
> Sitz der Gesellschaft: Feldkirchen bei Muenchen
> Geschaeftsfuehrer: Peter Gleissner, Christian Lamprechter, 
> Hannes Schwaderer, Douglas Lusk
> Registergericht: Muenchen HRB 47456
> Ust.-IdNr./VAT Registration No.: DE129385895
> Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
> 
> 


  reply	other threads:[~2012-09-10 15:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30  9:52 Mircea Gherzan
2012-08-30 14:44 ` Marc Khouzam
2012-08-30 17:47   ` Mircea Gherzan
2012-08-30 17:52     ` Marc Khouzam
2012-09-10 14:09       ` Pedro Alves
2012-09-10 14:48         ` Mircea Gherzan
2012-09-10 15:04           ` Marc Khouzam [this message]
2012-09-11 16:38 ` Tom Tromey

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=F7CE05678329534C957159168FA70DEC5E118AA286@EUSAACMS0703.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mgherzan@gmail.com \
    --cc=mircea.gherzan@intel.com \
    --cc=palves@redhat.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