From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sourceware.cygnus.com
Subject: RE: Windows NT Failing on XRef Generation.
Date: Thu, 08 Feb 2001 20:29:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010208202322.13626E-100000@cse.cygnus.com> (raw)
In-Reply-To: <8F1BE54DECC1D211BB2500105A9CA42101C1C82E@admin1.astralpoint>
On Thu, 8 Feb 2001, Story, Lenny wrote:
> Well,
>
> I can reproduce it 100% of the time on my code base....
> i've attached the Dr.Watson log entry for it....it should
> help you determine what is happening....I HOPE you keep the
> map..and list files....it will be your only way to corrolate
> the minimal assembly dump with the code...
When we say "can you reproduce the problem", the correct
answer is not "yes" :) We need you to create a small
one file example that will crash the parser. Trim
your code down to a very small file that still
crashes and then post it to the list. We are not
going to go rummaging around in your core dumps,
you need to provide a small example that
demonstrates the problem.
Mo DeJong
Red Hat Inc
next prev parent reply other threads:[~2001-02-08 20:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 20:16 Story, Lenny
2001-02-08 20:29 ` Mo DeJong [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-09 18:29 Story, Lenny
2001-02-09 11:41 Story, Lenny
2001-02-09 8:36 Story, Lenny
2001-02-09 9:57 ` Berek
2001-02-09 10:45 ` Kenneth Luke
2001-02-09 12:01 ` Mo DeJong
2001-02-09 12:27 ` Timothy M. Shead
2001-02-08 20:16 Story, Lenny
2001-02-08 16:15 Story, Lenny
2001-02-08 12:14 Story, Lenny
2001-02-08 12:25 ` Ian Roxborough
2001-02-08 9:52 dave.banham
2001-02-08 9:05 Story, Lenny
2001-02-08 9:55 ` Syd Polk
2001-02-08 11:25 ` Berek
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.1010208202322.13626E-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).