From: Weimin Pan <weimin.pan@oracle.com>
To: <qiyaoltc@gmail.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH v4] gdb: ADI support
Date: Tue, 01 Aug 2017 23:30:00 -0000 [thread overview]
Message-ID: <c3322bb7-87ac-4fa9-96ab-7f0544b95f44@default> (raw)
----- Original Message -----
> From: weimin.pan@oracle.com
> To: qiyaoltc@gmail.com
> Cc: gdb-patches@sourceware.org
> Sent: Tuesday, August 1, 2017 10:41:48 AM GMT -08:00 US/Canada Pacific
> Subject: Re: [PATCH v4] gdb: ADI support
>
> Thanks for your suggestions. There are 3 failures however.
>
>
> On 8/1/2017 7:10 AM, Yao Qi wrote:
> > Wei-min Pan <weimin.pan@oracle.com> writes:
> >
> >> (gdb) PASS: gdb.arch/sparc64-adi.exp: continue to breakpoint: continue
> >> to line breakpoint in main
> >> adi x shmaddr^M
> >> 0xfff800010002c000: 0 ^M
> > gdb_test "adi x shmaddr" "${hex}00:\t0" "examine ADI"
>
> It will pass if changed to
>
> gdb_test "adi x shmaddr" "${hex}00:.*\t0.*" "examine ADI"
Or change it to:
gdb_test "adi x shmaddr" "${hex}00:\t0 " "examine ADI"
>
>
> > 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"
>
> >> (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"
next reply other threads:[~2017-08-01 23:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 23:30 Weimin Pan [this message]
2017-08-02 7:55 ` Yao Qi
2017-08-02 18:00 ` Wei-min Pan
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=c3322bb7-87ac-4fa9-96ab-7f0544b95f44@default \
--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