Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: dje@google.com, brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: too many "no debugging symbols found" messages from shared libs
Date: Fri, 21 Nov 2008 22:08:00 -0000	[thread overview]
Message-ID: <ud4gpjej2.fsf@gnu.org> (raw)
In-Reply-To: <5186.86.86.3.213.1227272244.squirrel@webmail.xs4all.nl>

> Date: Fri, 21 Nov 2008 13:57:24 +0100 (CET)
> From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
> Cc: "Eli Zaretskii" <eliz@gnu.org>, brobecker@adacore.com,
>         gdb-patches@sourceware.org
> 
> Sorry I'm a bit late in this discussion, but I do really like the messages
> about missing symbol info for shared libraries.  To me they provide an
> important hint that my debugging session is likely to run into problems at
> some point.

You can still have that, just set the verbose option on.


  reply	other threads:[~2008-11-21 15:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 19:24 Mark Kettenis
2008-11-21 22:08 ` Eli Zaretskii [this message]
2008-11-22  4:43   ` Doug Evans
2008-11-22  6:38     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2008-11-22 16:49 Mark Kettenis
2008-11-22 17:49 ` Doug Evans
2008-11-22 21:41   ` Eli Zaretskii
2008-11-24  3:23     ` Paul Pluzhnikov
2008-11-24 16:54       ` Eli Zaretskii
2008-11-24 19:42         ` Doug Evans
2008-10-03 21:35 Doug Evans
2008-10-30  5:19 ` Joel Brobecker
2008-11-07 22:45   ` Doug Evans
2008-11-08  9:15     ` Eli Zaretskii
2008-11-10 16:46       ` Daniel Jacobowitz
2008-11-10 18:32         ` Joel Brobecker
2008-11-10 20:33         ` Eli Zaretskii
2008-11-10 20:51           ` Daniel Jacobowitz
2008-11-11  5:03             ` Eli Zaretskii
2008-11-11  5:34               ` Daniel Jacobowitz
2008-11-21 18:46                 ` Doug Evans
2008-11-21 19:16                   ` Eli Zaretskii

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=ud4gpjej2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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