From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 13/13] Document "no debug info debugging" improvements
Date: Thu, 13 Jul 2017 16:11:00 -0000 [thread overview]
Message-ID: <83shi0gvum.fsf@gnu.org> (raw)
In-Reply-To: <1499959929-29497-14-git-send-email-palves@redhat.com> (message from Pedro Alves on Thu, 13 Jul 2017 16:32:09 +0100)
> From: Pedro Alves <palves@redhat.com>
> Date: Thu, 13 Jul 2017 16:32:09 +0100
>
> New in v2: updated/rewritten to describe that the simpler cast syntax
> assumes the function is prototyped.
>
> Here's the documentation bits for all the improvements.
>
> Note that the original "weak alias functions" paragraph ends up
> disappearing, because this patch, which I'm considering kind of part
> of this series, makes the alias case Just Work:
> https://sourceware.org/ml/gdb-patches/2017-07/msg00018.html
>
> gdb/ChangeLog:
> yyyy-mm-dd Pedro Alves <palves@redhat.com>
>
> * NEWS (Safer support for debugging with no debug info): New.
>
> gdb/doc/ChangeLog:
> yyyy-mm-dd Pedro Alves <palves@redhat.com>
>
> * gdb.texinfo (Variables) <Program Variables>: Document inspecting
> no-debug-info variables.
> (Symbols) <Examining the Symbol Table>: Document inspecting
> no-debug-info types.
> (Calling) <Calling functions with no debug info>: New subsection,
> documenting calling no-debug-info functions.
> (Non-debug DLL Symbols) <Working with Minimal Symbols>: Update.
Same comments as before.
Thanks.
next prev parent reply other threads:[~2017-07-13 16:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 15:32 [PATCH v2 00/13] No-debug-info debugging improvements Pedro Alves
2017-07-13 15:32 ` [PATCH v2 05/13] evaluate_subexp_standard: Eliminate one goto Pedro Alves
2017-07-13 15:32 ` [PATCH v2 02/13] Stop assuming no-debug-info functions return int Pedro Alves
2017-07-13 15:32 ` [PATCH v2 10/13] Handle "p S::method()::static_var" in the C++ parser Pedro Alves
2017-07-13 15:32 ` [PATCH v2 11/13] Handle "p 'S::method()::static_var'" (quoted) in symbol lookup Pedro Alves
2017-07-13 15:32 ` [PATCH v2 01/13] Fix calling prototyped functions via function pointers Pedro Alves
2017-07-13 15:32 ` [PATCH v2 06/13] evaluate_subexp_standard: Remove useless assignments Pedro Alves
2017-07-13 15:32 ` [PATCH v2 09/13] Eliminate UNOP_MEMVAL_TLS Pedro Alves
2017-07-13 15:32 ` [PATCH v2 03/13] Introduce OP_VAR_MSYM_VALUE Pedro Alves
2017-07-13 15:37 ` [PATCH v2 12/13] Make "p S::method() const::static_var" work too Pedro Alves
2017-07-13 15:38 ` [PATCH v2 08/13] Stop assuming no-debug-info variables have type int Pedro Alves
2017-12-07 23:30 ` [RFA] Adjust gdb.arch/i386-sse-stack-align.exp print statement Sergio Durigan Junior
2017-12-08 10:47 ` Pedro Alves
2017-12-08 16:28 ` Sergio Durigan Junior
2017-07-13 15:38 ` [PATCH v2 13/13] Document "no debug info debugging" improvements Pedro Alves
2017-07-13 16:11 ` Eli Zaretskii [this message]
2017-07-13 16:31 ` Pedro Alves
2017-07-13 17:54 ` Eli Zaretskii
2017-07-13 15:38 ` [PATCH v2 07/13] evaluate_subexp_standard: Factor out OP_VAR_VALUE handling Pedro Alves
2017-07-13 15:39 ` [PATCH v2 04/13] Make ptype/whatis print function name of functions with no debug info too Pedro Alves
2017-09-04 19:21 ` [PATCH v2 00/13] No-debug-info debugging improvements 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=83shi0gvum.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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