Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: rth@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: dwarf2-frame clobbers memory
Date: Sun, 01 Jun 2003 09:20:00 -0000	[thread overview]
Message-ID: <200306010920.h519KZMQ002879@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20030601074733.GA12207@redhat.com> (message from Richard Henderson on Sun, 1 Jun 2003 00:47:33 -0700)

   Date: Sun, 1 Jun 2003 00:47:33 -0700
   From: Richard Henderson <rth@redhat.com>

   On Sat, May 31, 2003 at 08:36:21PM -0700, Richard Henderson wrote:
   > At the following traceback, memmove is overwriting the "help"
   > command, which results in a segv on the next command.  Is this
   > enough to track down the problem?

   Nevermind, found it.  Let us remember how pointer arithmetic works.  ;-)

Thanks!  I went ahead and committed this.

Mark


      reply	other threads:[~2003-06-01  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-01  3:38 Richard Henderson
2003-06-01  7:49 ` Richard Henderson
2003-06-01  9:20   ` Mark Kettenis [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=200306010920.h519KZMQ002879@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=gdb-patches@sources.redhat.com \
    --cc=rth@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