From: Pedro Alves <pedro@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Tristan Gingold <gingold@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Fix false warning: Shared library is missing debugging information.
Date: Mon, 11 Jan 2010 16:14:00 -0000 [thread overview]
Message-ID: <201001111614.22335.pedro@codesourcery.com> (raw)
In-Reply-To: <20100111160720.GB12356@host0.dyn.jankratochvil.net>
On Monday 11 January 2010 16:07:20, Jan Kratochvil wrote:
> 2010-01-11 Jan Kratochvil <jan.kratochvil@redhat.com>
> Tristan Gingold <gingold@adacore.com>
>
> * solib.c (info_sharedlibrary_command): Replace
> objfile_has_partial_symbols and objfile_has_full_symbols calls by
> objfile_has_symbols.
>
This is OK. Thanks.
--
Pedro Alves
next prev parent reply other threads:[~2010-01-11 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 15:13 Jan Kratochvil
2010-01-11 15:21 ` Tristan Gingold
2010-01-11 16:08 ` Jan Kratochvil
2010-01-11 16:14 ` Pedro Alves [this message]
2010-01-11 16:31 ` Jan Kratochvil
2010-01-11 18:08 ` Tom Tromey
2010-01-11 15:23 ` Pedro Alves
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=201001111614.22335.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=jan.kratochvil@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