Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: hacky fix for PR 12406
Date: Thu, 12 Jan 2012 11:40:00 -0000	[thread overview]
Message-ID: <20120112112533.GA4183@redhat.com> (raw)
In-Reply-To: <m34nw26pct.fsf@fleche.redhat.com>

Tom Tromey wrote:
> I would like to get some feedback on this.
> 
> PR 12406 concerns what is printed when stop-on-solib-events is set:
> 
>     (gdb) set stop-on-solib-events 1
>     (gdb) r
>     Starting program: /tmp/q 
>     Stopped due to shared library event
> 
> What is missing here is any indication of what library was loaded.
> 
> 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

Could this be a separate option, trace-solib-events maybe?  It seems
like this printing might also be useful when stop-on-solib-events is
off.

Also, as Jan said, it would be nice to have unload notifications too.

> I could not find a good way to get the information about what
> library was loaded from the library-loading code to the bpstat_print
> code.  This approach seems like a hack to me -- so I was wondering
> if anyone has a better suggestion.

I like Joel's idea of a flag, it's what I'd try.  You would probably
need to do something like that for unload notifications anyway.

Cheers,
Gary

-- 
http://gbenson.net/


      parent reply	other threads:[~2012-01-12 11:25 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
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 [this message]

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=20120112112533.GA4183@redhat.com \
    --to=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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