From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com, sergiodj@redhat.com
Subject: Re: [PATCH 2/4] python support for fetching separate debug files: have_debug_info
Date: Fri, 21 Nov 2014 07:41:00 -0000 [thread overview]
Message-ID: <837fyp57bu.fsf@gnu.org> (raw)
In-Reply-To: <yjt2d28ho9cw.fsf@ruffy.mtv.corp.google.com>
> From: Doug Evans <dje@google.com>
> Date: Thu, 20 Nov 2014 13:22:39 -0800
>
> This patch provides an API call to determine whether debug information
> is present. It's based on the same test that gdb internally uses
> to decide whether to look for separate debug files.
OK for the documentation parts.
Btw, I wonder why this is useful, given this caveat:
> +Note that a program compiled without @samp{-g} may still have some debug
> +information, e.g., from the @code{C} runtime. Thus a value of @code{True}
> +for this attribute does not mean that debug information is present for
> +every source file in the program. It only means that debug information
> +is present for at least one source file.
If this attribute cannot be relied upon, why is it a good idea to
expose it to Python?
next prev parent reply other threads:[~2014-11-21 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 21:22 Doug Evans
2014-11-21 7:41 ` Eli Zaretskii [this message]
2014-11-21 17:34 ` Doug Evans
2014-11-21 19:51 ` Eli Zaretskii
2014-11-21 20:22 ` Doug Evans
2014-11-22 8:04 ` Eli Zaretskii
2014-11-24 21:06 ` Doug Evans
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=837fyp57bu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@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