From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org, Simon Marchi <simon.marchi@ericsson.com>
Subject: Re: [PATCH][gdb/exp] Fix exception when printing optimized out vla
Date: Wed, 25 Jul 2018 19:00:00 -0000 [thread overview]
Message-ID: <87a7qf16pi.fsf@tromey.com> (raw)
In-Reply-To: <20180719152758.24vnhbekc4hdlwax@delia> (Tom de Vries's message of "Thu, 19 Jul 2018 17:27:59 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> when compiling vla-optimized-out.c with -O3 and a recent gcc, and trying to
Tom> print the vla a in f1, we run into this gdb exception:
Tom> ...
Tom> Cannot find matching parameter at DW_TAG_call_site 0x4003be at main
Tom> ...
Tom> This is a regression introduced by 42dc7699a2 "[gdb/exp] Fix printing of type
Tom> of optimized out vla".
Tom> This patch fixes the regression by wrapping the ctx.eval call in
Tom> dwarf2_locexpr_baton_eval in try/catch, similar to what is done in
Tom> dwarf2_evaluate_loc_desc_full.
Tom> Build and reg-tested on x86_64-linux.
Tom> OK for trunk?
Thanks for the patch.
This is ok.
Tom
prev parent reply other threads:[~2018-07-25 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 15:27 Tom de Vries
2018-07-25 19:00 ` 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=87a7qf16pi.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--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