From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sourceware.cygnus.com
Subject: RE:Windows NT Failing on XRef Generation
Date: Tue, 13 Feb 2001 23:05:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010213230213.19319D-100000@cse.cygnus.com> (raw)
In-Reply-To: <802569F2.0046C935.00@venus.cwb.com>
On Tue, 13 Feb 2001, Darren Syzling wrote:
> We've also seen a crash on xref generation under NT with the 4.5.2 stable
> release. Unfortunately this occurs within our product code base and is a little
> difficult to extract a repeatable test case.
I know how hard it is to trim down a test case, but we really
need one if we are to be of any help tracking this down. Finding
bugs in compilers and parsers is really really hard, it is
just about impossible without a test case.
Mo DeJong
Red Hat Inc
next prev parent reply other threads:[~2001-02-13 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 4:55 Darren Syzling
2001-02-13 9:15 ` SourceNav Symbol Browser Closed Bill Munday
2001-02-13 13:29 ` Ian Roxborough
2001-02-13 23:05 ` Mo DeJong [this message]
2001-02-14 8:51 ` Grep Editor function Bill Munday
2001-02-14 10:04 RE:Windows NT Failing on XRef Generation Darren Syzling
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.SOL.3.91.1010213230213.19319D-100000@cse.cygnus.com \
--to=mdejong@cygnus.com \
--cc=sourcenav@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).