Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org,  jan.kratochvil@redhat.com,
	 sanjoyd@sourceware.org
Subject: Re: Missing test cases for jit-reader interface
Date: Wed, 25 Feb 2015 16:23:00 -0000	[thread overview]
Message-ID: <87egpeufib.fsf@igalia.com> (raw)
In-Reply-To: <86y4nmvvme.fsf@gmail.com> (Yao Qi's message of "Wed, 25 Feb 2015	15:50:01 +0000")

On Wed 25 Feb 2015 16:50, Yao Qi <qiyaoltc@gmail.com> writes:

>> +if { (![istarget x86_64-*-*] && ![istarget i?86-*-*]) || ![is_lp64_target] } {
>> +    return -1;
>> +}
>
> I don't see any reason why this test is arch specific.  We can remove
> such checking, IMO.

The test is arch-specific because it has a simple x86 "jit".  See
jithost.c.

>> +if { ![isnative] } {
>> +    return -1
>> +}
>
> and remove it too.

Does it not need to be this way?  If you are debugging from a big-endian
host, you will read the addresses wrong from the inferior, as the
jit-reader .so reads the values directly.  (Seems to me anyway.)

>> +gdb_load_shlibs "${jit_reader_bin}"
>> +
>
> It should be moved into jit_reader_test, after clean_restart, otherwise,
> we'll get the following errors if I run it with --target_board=native-gdbserver.

ACK.  Will update.

Thanks for the review,

Andy


  reply	other threads:[~2015-02-25 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 10:23 Andy Wingo
2015-02-23 13:11 ` Andy Wingo
2015-02-25  7:38   ` Sanjoy Das
2015-02-25 15:50   ` Yao Qi
2015-02-25 16:23     ` Andy Wingo [this message]
2015-02-25 22:39       ` Yao Qi
2015-02-26  9:02         ` Andy Wingo
2016-06-17 18:56     ` [pushed] " Pedro Alves

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=87egpeufib.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=qiyaoltc@gmail.com \
    --cc=sanjoyd@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