Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Make gdb1476.exp more robust
Date: Wed, 07 Jan 2004 22:41:00 -0000	[thread overview]
Message-ID: <20040107224146.GA2280@nevyn.them.org> (raw)
In-Reply-To: <200401072213.i07MDiD1014224@elgar.kettenis.dyndns.org>

On Wed, Jan 07, 2004 at 11:13:44PM +0100, Mark Kettenis wrote:
> Peter Schauer pointed out to me that excuting code at address 0 might
> have ill effects on targets that don't have an MMU.  He suggested
> testing whether we could read from that address, and only run the
> tests if we can't.

I suppose that's some incentive for me to fix gdbserver... it currently
allows invalid reads.

> +# If we can examine what's at memory address 0, it is possible that we
> +# could also execute it.  This could pobably make us run away,

Typo, probably.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2004-01-07 22:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 22:13 Mark Kettenis
2004-01-07 22:41 ` Daniel Jacobowitz [this message]

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=20040107224146.GA2280@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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