From: Wei-min Pan <weimin.pan@oracle.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4] gdb: ADI support
Date: Wed, 02 Aug 2017 18:00:00 -0000 [thread overview]
Message-ID: <96ca9d77-8f57-59d2-ded2-afee72abc467@oracle.com> (raw)
In-Reply-To: <86379a4d55.fsf@gmail.com>
On 8/2/2017 12:55 AM, Yao Qi wrote:
> Weimin Pan <weimin.pan@oracle.com> writes:
>
>>> gdb_test "adi x shmaddr" "${hex}00:.*\t0.*" "examine ADI"
>> Or change it to:
>>
>> gdb_test "adi x shmaddr" "${hex}00:\t0 " "examine ADI"
>>
> Why does it print a trailing space? Can we remove it? It is from the
> for loop in adi_print_versions,
A trailing space is needed to separate tag values. I can change the code
so that no space is added for the last tag value:
if (tags[v_idx] == 0xff) /* no version tag */
printf_filtered ("-");
else
printf_filtered ("%1X", tags[v_idx]);
if (cnt > 1)
printf_filtered (" ");
and use your suggested "adi x" commands in the script.
> + for (int i = maxelts; i > 0 && cnt > 0; i--, cnt--)
> + {
> + if (tags[v_idx] == 0xff) /* no version tag */
> + printf_filtered ("- ");
> + else
> + printf_filtered ("%1X ", tags[v_idx]);
> + ++v_idx;
> + }
>
>>>
>>>> gdb_test "adi x/100 shmaddr" "${hex}00:\t${newadi} ${newadi}" \
>>>> "examine new ADI"
>>> It will pass if changed to:
>>>
>>> gdb_test "adi x/100 shmaddr" "${hex}00:.*\t${newadi} ${newadi}.*" \
>>> "examine new ADI"
>> Or change it to:
>>
>> gdb_test "adi x/100 shmaddr" "${hex}00:\t${newadi} ${newadi} " \
>> "examine new ADI"
>>
> Likewise.
>
>>>>> (gdb) PASS: gdb.arch/sparc64-adi.exp: reset ADI
>>>>> continue^M
>>>>> Continuing.^M
>>>>> ^M
>>>>> Program received signal SIGSEGV, Segmentation fault^M
>>>>> ADI precise mismatch while accessing address 0xfff8000100048000.^M
>>>>> 0xfff8000100129f38 in adi_set_version () from /usr/lib64/libadi.so^M
>>>> gdb_test "continue" \
>>>> [multi_line "Program received signal SIGSEGV, Segmentation fault" \
>>>> "ADI precise mismatch while accessing address $hex" ] \
>>>> "continue to sigsegv"
>>> And it will pass if changed to
>>>
>>> gdb_test "continue" \
>>> [multi_line ".*Program received signal SIGSEGV, Segmentation fault.*" \
>>> ".*ADI precise mismatch while accessing address $hex.*" ] \
>>> "continue to sigsegv"
>> Or change it to:
>>
>> gdb_test "continue" \
>> [multi_line "Program received signal SIGSEGV, Segmentation fault.*" \
>> "ADI precise mismatch while accessing address $hex.*" ] \
>> "continue to sigsegv"
> That is OK.
>
next prev parent reply other threads:[~2017-08-02 18:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 23:30 Weimin Pan
2017-08-02 7:55 ` Yao Qi
2017-08-02 18:00 ` Wei-min Pan [this message]
2017-08-04 11:57 ` Yao Qi
-- strict thread matches above, loose matches on Subject: below --
2017-08-04 22:46 Weimin Pan
2017-07-25 22:37 Weimin Pan
2017-07-25 19:19 Weimin Pan
2017-07-25 20:18 ` Simon Marchi
2017-07-25 21:03 ` Jose E. Marchesi
2017-07-19 0:49 Weimin Pan
2017-07-25 15:16 ` Yao Qi
2017-07-25 15:31 ` Jose E. Marchesi
2017-07-25 16:44 ` Yao Qi
2017-07-26 21:12 ` Wei-min Pan
2017-07-27 11:17 ` Yao Qi
2017-07-27 16:34 ` Wei-min Pan
2017-07-28 10:30 ` Yao Qi
2017-07-28 16:34 ` Wei-min Pan
[not found] ` <868tj3ml8s.fsf@gmail.com>
2017-08-01 17:41 ` Wei-min Pan
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=96ca9d77-8f57-59d2-ded2-afee72abc467@oracle.com \
--to=weimin.pan@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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