Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: nick clifton <nickc@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: dj@redhat.com, gdb-patches@sourceware.org
Subject: Re: RFA: V850 sim: various fixes.
Date: Mon, 10 Sep 2012 15:41:00 -0000	[thread overview]
Message-ID: <504E0877.2040202@redhat.com> (raw)
In-Reply-To: <CAJaTeTo5ReU4CA+izqgM6yP5TcpubCX6DfHsJtE-QN86GwdQ4g@mail.gmail.com>

Hi Mike,

>>    It also adds a snippet of code to catch attempts to
>>    execute code via a NULL pointer.
>
> usually the simulator represents the hardware.  so if the hardware has
> memory at address 0 and someone were to load up an image with code
> there, there's nothing invalid when it comes to jumping there.

Personally I see the simulator as more of a testing and debugging tool. 
  It does not try to be hardware accurate - it does not model the cache 
for example - so adding a feature that helps catch program errors, even 
if it not strictly modelling the hardware, seems OK to me.

> what i do on the Blackfin side when it comes to testing is to have the
> ELF manually pad the start with insns that'll trigger an exception
> (just like it would on the hw).  then i set the entry point beyond
> that.

Another fine approach.  I'll see what DJ thinks, but I will be happy
to remove the NULL trapping part of the patch if he does not like it.

Cheers
   Nick



  reply	other threads:[~2012-09-10 15:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 10:21 Nick Clifton
2012-09-10 15:27 ` Mike Frysinger
2012-09-10 15:41   ` nick clifton [this message]
2012-09-10 16:56     ` Mike Frysinger
2012-09-10 15:50   ` DJ Delorie
2012-09-10 16:33     ` nick clifton
2012-09-13  1:13       ` DJ Delorie

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=504E0877.2040202@redhat.com \
    --to=nickc@redhat.com \
    --cc=dj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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