Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Manoj Iyer <manjo@austin.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC] GDB prints internal error with C++ application produced by XLC.
Date: Thu, 14 Apr 2005 16:15:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0504141147030.2316@lazy> (raw)
In-Reply-To: <20050414030914.GA23471@nevyn.them.org>


Daniel,

> > No, don't do that.

Ok, that is good to know... :-)

> By the way, I have since posted a more complete patch which should
> obsolete this one.  If you'd like, you could try it on your test.

Which is fine by me, coz all I wanted was to see a fix for that error
message. Did you include my patch in yours? Coz I remember a conversation
where u had mentioned that you were waiting for my patch to makeit into
the source base.

Thanks
Manjo


      reply	other threads:[~2005-04-14 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14  1:38 Manoj Iyer
2005-04-14  3:08 ` Daniel Jacobowitz
2005-04-14  3:09   ` Daniel Jacobowitz
2005-04-14 16:15     ` Manoj Iyer [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=Pine.LNX.4.58.0504141147030.2316@lazy \
    --to=manjo@austin.ibm.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