From: Joe Pallas <pallas@cs.stanford.edu>
To: Ben Elliston <bje@redhat.com>
Cc: sourcenav@sourceware.cygnus.com
Subject: Re: Help with dbimp crash?
Date: Tue, 29 Aug 2000 07:57:00 -0000 [thread overview]
Message-ID: <v04210100b5d17ec7cf64@[10.8.53.6]> (raw)
In-Reply-To: <Pine.LNX.4.21.0008291009180.10111-100000@moshpit.cygnus.com>
At 10:10 AM +1100 8/29/00, Ben Elliston wrote:
>The parsers pipe their output into dbimp.
>Do you have an example of input that causes this problem?
I do, but it's not that simple. When I feed the saved trace back
into dbimp, it insists on reopening the source files and gets unhappy
if they're not there. I'm sure this has something to do with the
mysterious fact that the c++ parser is linked into dbimp. This makes
it hard for me to provide a simple test case (the source files are
proprietary).
joe
prev parent reply other threads:[~2000-08-29 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-28 15:59 Joseph Pallas
2000-08-28 16:09 ` Syd Polk
2000-08-28 16:10 ` Ben Elliston
2000-08-28 16:10 ` Ben Elliston
2000-08-29 7:57 ` Joe Pallas [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='v04210100b5d17ec7cf64@[10.8.53.6]' \
--to=pallas@cs.stanford.edu \
--cc=bje@redhat.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).