From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/3] Fix fails in gdb.mi on arm-none-eabi
Date: Thu, 18 Sep 2014 01:05:00 -0000 [thread overview]
Message-ID: <87vbolzqq9.fsf@codesourcery.com> (raw)
In-Reply-To: <1409533072-6152-1-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Mon, 1 Sep 2014 08:57:49 +0800")
Yao Qi <yao@codesourcery.com> writes:
> This series fixes some fails in mi-var-child.exp and
> mi-var-display.exp, which are caused by printed symbol on address
> zero. One of them is fixed by "set print symbol" off, and that is
> what patch 1/3 does. Patch 2/3 is a refactor patch, which uses
> mi_varobj_update in tests to simplify them.
>
> The cause of the rest of fails is that function pointers are NULL,
> and they point to a code symbol _ftext on address zero. We can
> relax pattern to match both "0x0" and "0x0 <_ftext>", but I didn't
> fix it in this way. Instead, I explicitly assign function address
> to these function pointers, so the output becomes "$hex <$func_name>"
> on all the targets. See details in patch 3/3.
>
> The patch series is tested on x86_64-linux with native and gdbserver,
> and arm-none-eabi.
Patch 1 is pushed in. Ping patch 2 and patch 3.
https://sourceware.org/ml/gdb-patches/2014-09/msg00002.html
https://sourceware.org/ml/gdb-patches/2014-09/msg00003.html
--
Yao (齐尧)
next prev parent reply other threads:[~2014-09-18 1:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 1:02 Yao Qi
2014-09-01 1:03 ` [PATCH 2/3] Use mi_varobj_update in mi-var-child.exp and mi2-var-child.exp Yao Qi
2014-10-14 11:48 ` Yao Qi
2014-09-01 1:03 ` [PATCH 1/3] Set print symbol off in mi-var-display.exp Yao Qi
2014-09-09 2:12 ` Yao Qi
2014-09-01 1:04 ` [PATCH 3/3] Fix fail in mi-var-child.exp and mi-var-display.exp Yao Qi
2014-10-14 11:49 ` Yao Qi
2014-09-18 1:05 ` Yao Qi [this message]
2014-09-30 14:04 ` [PATCH 0/3] Fix fails in gdb.mi on arm-none-eabi Yao Qi
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=87vbolzqq9.fsf@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).