This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/4] python support for fetching separate debug files: have_debug_info
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Doug Evans <dje at google dot com>
- Cc: gdb-patches at sourceware dot org, palves at redhat dot com, sergiodj at redhat dot com
- Date: Fri, 21 Nov 2014 09:41:25 +0200
- Subject: Re: [PATCH 2/4] python support for fetching separate debug files: have_debug_info
- Authentication-results: sourceware.org; auth=none
- References: <yjt2d28ho9cw dot fsf at ruffy dot mtv dot corp dot google dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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?