From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Andreas Schwab <schwab@suse.de>
Subject: Re: [PATCH v2] gdb/hppa-tdep.c: Fix logical working flow typo issue
Date: Sun, 23 Nov 2014 13:40:00 -0000 [thread overview]
Message-ID: <5471E3D5.10006@gmail.com> (raw)
In-Reply-To: <20141123063849.GA7636@adacore.com>
On 11/23/2014 02:38 PM, Joel Brobecker wrote:
> Chen,
>
>> Is this patch OK, it is part of checking saving registers in the stack,
>> it tries to recognize the saving instructions "stb, stw(m), or std", so
>> can continue checking.
>>
>> Excuse me, I have no related environments for a test, I assumed that the
>> original author knew about the working flow, then wrote the related
>> function.
>>
>> If need additional analyzing, please let me know (better to let me know
>> what I need try, next).
>
> Thank you for the patch, but lack of access to an environment where
> you can test is an issue. I would be an entirely different context
> if the fix was obvious, but it isn't unless perhaps you start
> opening HP-PA assembly manuals; and I don't honestly see much interest
> in HP-PA anymore.
>
I shall try to find the related assembly reference (although it is not
quite easy for me, and may be fail to get it), or get parisc related
members confirmation.
Hope I can get related proof (related documents, or related members
confirmation) within next month (2014-12-31), although I am not quite
sure whether I can finish or not.
> And if you do not have access to an environment for a test, how did
> you come about this issue? Does the lack of evironment mean lack of
> the software (tcl, expect, dejagnu), or lack of hardware?
>
It is lack of hardware and related software. And I found it firstly by
gcc5 compiler warning, then read through the code (together with some
gdb members), found it should be an issue.
Thanks.
--
Chen Gang
Open share and attitude like air water and life which God blessed
next prev parent reply other threads:[~2014-11-23 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 15:39 Chen Gang
2014-10-22 15:41 ` Chen Gang
2014-10-24 22:41 ` Chen Gang
2014-11-23 6:38 ` Joel Brobecker
2014-11-23 13:40 ` Chen Gang [this message]
2014-12-07 22:31 ` Chen Gang
2014-12-08 3:15 ` Joel Brobecker
2014-12-08 4:20 ` Chen Gang
2014-12-08 5:08 ` Joel Brobecker
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=5471E3D5.10006@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@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