From: Jeffrey A Law <law@cygnus.com>
To: chris@lslsun.epfl.ch (Christian Iseli)
Cc: egcs@cygnus.com
Subject: Re: Small problem in cse
Date: Mon, 20 Oct 1997 09:43:00 -0000 [thread overview]
Message-ID: <4774.877365906@hurl.cygnus.com> (raw)
In-Reply-To: <199710200842.KAA16565@lslsun17.epfl.ch>
In message < 199710200842.KAA16565@lslsun17.epfl.ch >you write:
> > In message < 199710172043.WAA24596@Rivendell.MiddleEarth.net >you write:
> > > I've received a segfault from cc1 due to a NULL dereference in cse.c.
> > > The following trivial patch cures the problem.
> > Yes, but _why_ is classp NULL?
>
> classp is not NULL, but classp->first_same_value is NULL, and later
> dereferenced. I don't *know* why that field is NULL, I just assumed
> that no same value had been seen yet...
Sorry, I meant to say why is classp->first_same_value NULL?
From my review of the code I don't see that classp->first_same_value should
ever be NULL -- thus I suspect something has gone wrong elsewhere that
needs to be investigated.
But I could be wrong, since you've got a target & testcase which triggers
this problem you'll need to do some of the analysis.
Thanks,
jeff
next prev parent reply other threads:[~1997-10-20 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-20 1:43 Christian Iseli
1997-10-20 9:43 ` Jeffrey A Law [this message]
1997-10-20 13:28 ` Christian Iseli
1997-10-24 16:16 ` multiple_of_p change Christian Iseli
1997-11-02 21:29 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1997-12-02 7:10 Small problem in cse Christian Iseli
1997-12-06 7:51 ` Jeffrey A Law
1997-10-28 7:06 Christian Iseli
1997-10-28 7:11 ` Joern Rennecke
1997-10-26 23:47 Christian Iseli
1997-10-27 6:02 ` Joern Rennecke
1997-10-17 13:44 Christian Iseli
1997-10-17 19:06 ` Jeffrey A Law
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=4774.877365906@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=chris@lslsun.epfl.ch \
--cc=egcs@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).