From: Daniel Jacobowitz <drow@false.org>
To: Greg Law <greg@greglaw.net>
Cc: gdb@sourceware.org
Subject: Re: decode_variable's use of not_found_ptr
Date: Mon, 24 Apr 2006 06:13:00 -0000 [thread overview]
Message-ID: <20060423155707.GA29228@nevyn.them.org> (raw)
In-Reply-To: <444B554B.10608@greglaw.net>
On Sun, Apr 23, 2006 at 11:22:03AM +0100, Greg Law wrote:
> Yes - 6.3 doesn't have this issue.
Strange, since I've been seeing something much like this for years.
Can you describe exactly how to reproduce it?
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-04-23 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 13:00 Greg Law
2006-04-22 16:32 ` Dave Korn
2006-04-22 21:21 ` Dave Korn
2006-04-22 21:36 ` Greg Law
2006-04-23 10:22 ` Nick Roberts
2006-04-23 15:57 ` Daniel Jacobowitz
2006-04-24 6:05 ` Greg Law
2006-04-24 6:13 ` 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=20060423155707.GA29228@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=greg@greglaw.net \
/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