Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Tom Tromey'" <tromey@redhat.com>
Cc: "'Pedro Alves'" <palves@redhat.com>,
	       "'gdb-patches@sourceware.org'"
	<gdb-patches@sourceware.org>
Subject: RE: [4/4] RFC: implement catch load and catch unload
Date: Tue, 24 Jan 2012 20:36:00 -0000	[thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC578E892296@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <m3wr8haq1c.fsf@fleche.redhat.com>

> -----Original Message-----
> From: Tom Tromey [mailto:tromey@redhat.com] 
> Sent: Tuesday, January 24, 2012 1:56 PM
> To: Marc Khouzam
> Cc: 'Pedro Alves'; 'gdb-patches@sourceware.org'
> Subject: Re: [4/4] RFC: implement catch load and catch unload
> 
> >>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:
> 
> Marc> Is the change already in HEAD?  I can test with that 
> just to be sure
> Marc> I haven't missed something.
> 
> Yes; it is also in 7.4:
> 
> 2011-11-22  Tom Tromey  <tromey@redhat.com>
> 
> 	PR mi/8444:
> 	* mi/mi-common.h (EXEC_ASYNC_SOLIB_EVENT, EXEC_ASYNC_FORK)
> 	(EXEC_ASYNC_VFORK, EXEC_ASYNC_SYSCALL_ENTRY)
> 	(EXEC_ASYNC_SYSCALL_RETURN, EXEC_ASYNC_EXEC): New constants.
> 	* mi/mi-common.c (async_reason_string_lookup): Add new reasons.
> 	* breakpoint.c (print_it_catch_fork, print_it_catch_vfork)
> 	(print_it_catch_syscall, print_it_catch_exec)
> 	(internal_bkpt_print_it): Use ui_out.  Emit stop reason.
> 	(bpstat_print): Add 'kind' argument.  Handle
> 	TARGET_WAITKIND_LOADED.
> 	* infrun.c (normal_stop): Update for bpstat_print change.  Don't
> 	handle TARGET_WAITKIND_LOADED here.
> 	* breakpoint.h (bpstat_print): Update.

Ok, looks ok with a single line change to use 'solib-event' instead
of 'shlib-event'.  Again, this is for the legacy/deprecated GDB
integration.  Our default integration is ok.

Until the next version of eclipse is released with
that fix, the legacy integration will stop at every solib event,
even if the user doesn't want it to.

Thanks Tom and Pedro for pointing this out.

Marc


  reply	other threads:[~2012-01-24 20:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 21:03 Tom Tromey
2012-01-19 22:04 ` Eli Zaretskii
2012-01-20 15:12   ` Tom Tromey
2012-01-20 17:40 ` Pedro Alves
2012-01-24 17:31   ` Tom Tromey
2012-01-24 19:40     ` Pedro Alves
2012-01-20 17:44 ` Yao Qi
2012-01-20 19:45 ` Pedro Alves
2012-01-24 17:07   ` Tom Tromey
2012-01-24 17:28     ` Marc Khouzam
2012-01-24 18:25       ` Tom Tromey
2012-01-24 18:32         ` Marc Khouzam
2012-01-24 19:15           ` Tom Tromey
2012-01-24 20:36             ` Marc Khouzam [this message]
2012-01-24 17:22   ` Tom Tromey
2012-01-24 19:17     ` Pedro Alves
2012-01-24 22:11 ` Tom Tromey
2012-01-25 11:06   ` Regression for gdb.mi/mi-nsmoribund.exp [Re: [4/4] RFC: implement catch load and catch unload] Jan Kratochvil
2012-01-25 11:18     ` Regression for gdb.base/solib-disc.exp [Re: Regression for gdb.mi/mi-nsmoribund.exp] Jan Kratochvil
2012-01-25 17:09       ` Tom Tromey
2012-01-25 17:27         ` Jan Kratochvil
2012-01-25 16:20     ` Regression for gdb.mi/mi-nsmoribund.exp [Re: [4/4] RFC: implement catch load and catch unload] Tom Tromey
2012-02-20  8:28   ` [commit] catch-load.exp: Fix racy FAILs " Jan Kratochvil

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=F7CE05678329534C957159168FA70DEC578E892296@EUSAACMS0703.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=tromey@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