Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Gary Benson <gbenson@redhat.com>
Subject: Re: RFC: hacky fix for PR 12406
Date: Thu, 12 Jan 2012 00:12:00 -0000	[thread overview]
Message-ID: <20120111224613.GA9123@host2.jankratochvil.net> (raw)
In-Reply-To: <m34nw26pct.fsf@fleche.redhat.com>

On Wed, 11 Jan 2012 19:55:30 +0100, Tom Tromey wrote:
> This patch changes the output to:
> 
>     (gdb) set stop-on-solib-events 1
>     (gdb) r
>     Starting program: /tmp/q 
>     [Inferior loaded library /lib64/ld-linux-x86-64.so.2]
>     Stopped due to shared library event

I find it OK, also an unload would be good to notify there.  There will still
be some no-operations stops without Gary's STAP-probe-in-ld.so.


Thanks,
Jan


  reply	other threads:[~2012-01-11 22:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 19:25 Tom Tromey
2012-01-12  0:12 ` Jan Kratochvil [this message]
2012-01-12  5:59 ` Joel Brobecker
2012-01-12 21:41   ` Tom Tromey
2012-01-13 15:48     ` Gary Benson
2012-01-12 11:40 ` Gary Benson

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=20120111224613.GA9123@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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