From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/symtab] Support DW_AT_main_subprogram with -readnow.
Date: Wed, 29 May 2019 13:37:00 -0000 [thread overview]
Message-ID: <87ef4h5qlg.fsf@tromey.com> (raw)
In-Reply-To: <20190505102520.GA5031@delia> (Tom de Vries's message of "Sun, 5 May 2019 12:25:22 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> DW_AT_main_subprogram is supported in normal mode in read_partial_die, but not
Tom> in -readnow mode.
Tom> Fix this by adding support for DW_AT_main_subprogram in read_func_scope.
Tom> Tested on x86_64-linux with native and RFC target board readnow (
Tom> https://sourceware.org/ml/gdb-patches/2019-05/msg00073.html ).
Tom> OK for trunk?
Thank you for the patch. This is ok.
Tom
prev parent reply other threads:[~2019-05-29 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 10:25 Tom de Vries
2019-05-05 11:42 ` [RFC] How to fix gdb.dwarf2/main-subprogram.exp with cc-with-gdb-index/cc-with-debug-names Tom de Vries
2019-05-10 7:57 ` Tom de Vries
2019-05-13 14:20 ` Tom de Vries
2019-05-17 15:08 ` [PING][PATCH][gdb/symtab] Support DW_AT_main_subprogram with -readnow Tom de Vries
2019-05-29 13:37 ` Tom Tromey [this message]
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=87ef4h5qlg.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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