From: "Dave Korn" <dave.korn@artimi.com>
To: "'Daniel Jacobowitz'" <drow@false.org>, <gdb@sourceware.org>
Subject: RE: Cygwin GDB crashes from cvs - solib
Date: Mon, 10 Apr 2006 21:34:00 -0000 [thread overview]
Message-ID: <01a601c65cca$cae85210$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <20060410180213.GA29243@nevyn.them.org>
On 10 April 2006 19:02, 'Daniel Jacobowitz' wrote:
> What you say is true for gdbarch. It is not quite true for target
> vectors, and I don't know of any other prior art for solibs.
Sorry, slight contextual laxness with the term "target vector" there, the
gdbarch is in fact what I was specifically thinking of when I wrote that,
although I was also thinking of bfd and gcc, which also have "target vectors",
and which generally require the pointers to be tested before use.
cheers,
DaveK
--
Can't think of a witty .sigline today....
prev parent reply other threads:[~2006-04-10 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 18:00 Daniel Jacobowitz
2006-04-10 18:02 ` Dave Korn
2006-04-10 18:08 ` Christopher Faylor
2006-04-14 13:43 ` 'Daniel Jacobowitz'
2006-04-10 18:10 ` 'Daniel Jacobowitz'
2006-04-10 21:34 ` Dave Korn [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='01a601c65cca$cae85210$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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