From: Pedro Alves <palves@redhat.com>
To: "Vörtler, Thilo" <thilo.voertler@coseda-tech.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PING] RE: [RFC][PATCH] - Fix pretty-printers which call the inferiors, mi-interface crashs
Date: Tue, 04 Oct 2016 17:41:00 -0000 [thread overview]
Message-ID: <7f4f079e-bb85-5a67-6445-8ab102b0742c@redhat.com> (raw)
In-Reply-To: <98af10fc7cb34b1baf4e28408ad6d782@EX132MBOX2B.de2.local>
Hi there,
Sorry for the delay. Thanks much for digging in and writing
the patch. It'd be really great if we could have a testcase in
the testsuite to exercise this. That'd help move the patch along,
and, it'd make sure we don't regress again in the future.
Thanks,
Pedro Alves
On 06/27/2016 03:35 PM, Vörtler, Thilo wrote:
>> -----Ursprüngliche Nachricht-----
>> Von: Vörtler, Thilo
>> Gesendet: Donnerstag, 2. Juni 2016 11:09
>> An: 'gdb-patches@sourceware.org' <gdb-patches@sourceware.org>
>> Betreff: [RFC][PATCH] - Fix pretty-printers which call the inferiors, mi-
>> interface crashs
>>
>> Hi,
>> as described in Bug 17437 the mi interface corrupts cached frames in the
>> list_arg_or_local function of mi-cmd-stack.c when a pretty-printer calls a
>> function of the inferior. To prevent this the frame_id is stored and used to
>> restore the frame after calling list_arg_or_local
>> - MI regressions were run and no effect through the patch was seen
>>
>> Is this patch okay?
>>
>> BR, Thilo
>>
>>
>> gdb/ChangeLog:
>>
>> 2016-06-02 Thilo Vörtler <thilo.voertler@coseda-tech.com>
>>
>> * mi-cmd-stack.c (list_args_or_locals) the mi interface corrupts
>> cached frames in the list_arg_or_local function of mi-cmd-stack.c
>> when
>> a pretty-printer calls a function of the inferior. To prevent this the
>> frame_id is stored and used to restore the frame after calling
>> list_arg_or_local
next prev parent reply other threads:[~2016-10-04 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 14:36 Vörtler, Thilo
2016-10-04 17:41 ` Pedro Alves [this message]
2016-07-15 9:04 Vörtler, Thilo
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=7f4f079e-bb85-5a67-6445-8ab102b0742c@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=thilo.voertler@coseda-tech.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