From: Yao Qi <qiyaoltc@gmail.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: Pedro Alves <palves@redhat.com>,
gdb-patches@sourceware.org, Yao Qi <qiyaoltc@gmail.com>
Subject: Re: [PATCH] S390: Add use of unavailable-stack frame ID
Date: Tue, 15 Mar 2016 08:12:00 -0000 [thread overview]
Message-ID: <86r3fcxirh.fsf@gmail.com> (raw)
In-Reply-To: <m3mvq5z7tl.fsf@oc1027705133.ibm.com> (Andreas Arnez's message of "Fri, 11 Mar 2016 10:23:50 +0100")
Andreas Arnez <arnez@linux.vnet.ibm.com> writes:
>> Seeing all these makes me want this:
>>
>> https://sourceware.org/ml/gdb-patches/2016-02/msg00778.html
>>
>> even more. :-)
>
> Agreed. It's on Yao's todo list, right? ;-) --
>
> https://sourceware.org/ml/gdb-patches/2016-02/msg00858.html
Yes, but it is in the bottom. Your patch is a good evidence that we
need to fix all "unavailable stack" stuff in target independent part.
--
Yao (齐尧)
prev parent reply other threads:[~2016-03-15 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 10:20 Andreas Arnez
2016-03-09 16:16 ` [PUSHED] " Andreas Arnez
2016-03-10 20:26 ` Pedro Alves
2016-03-11 9:24 ` Andreas Arnez
2016-03-15 8:12 ` Yao Qi [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=86r3fcxirh.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=arnez@linux.vnet.ibm.com \
--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