Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: save lots of memory
Date: Fri, 06 Nov 2009 19:23:00 -0000	[thread overview]
Message-ID: <8ac60eac0911061123ma992eddkf0a082983d76a56@mail.gmail.com> (raw)
In-Reply-To: <m3k4y3qzw7.fsf@fleche.redhat.com>

On Fri, Nov 6, 2009 at 10:19 AM, Tom Tromey <tromey@redhat.com> wrote:

> This patch implements both of these.

FYI:

patching file symfile.c
Hunk #1 FAILED at 3099.
Hunk #2 FAILED at 3124.
Hunk #3 succeeded at 3160 (offset -1 lines).
Hunk #4 succeeded at 3173 (offset -1 lines).
2 out of 4 hunks FAILED -- saving rejects to file symfile.c.rej




-- 
Paul Pluzhnikov


  reply	other threads:[~2009-11-06 19:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05  1:24 Tom Tromey
2009-11-05 17:28 ` Joel Brobecker
2009-12-27  3:40   ` Joel Brobecker
2009-11-05 19:59 ` Daniel Jacobowitz
2009-11-06 18:20   ` Tom Tromey
2009-11-06 19:23     ` Paul Pluzhnikov [this message]
2009-11-06 20:50       ` Tom Tromey
2009-11-16 18:41     ` Tom Tromey
2009-11-16 22:14       ` Tom Tromey

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=8ac60eac0911061123ma992eddkf0a082983d76a56@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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