From: rmoser <mlmoser@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Re: CRAP it crashes
Date: Sun, 27 Apr 2003 19:20:11 -0400 [thread overview]
Message-ID: <200304271920110140.02AAE835@smtp.comcast.net> (raw)
In-Reply-To: <200304271832150570.027F05E9@smtp.comcast.net>
*********** REPLY SEPARATOR ***********
On 4/27/2003 at 6:32 PM rmoser wrote:
>Segfault in fcomp_push() in test. Debugging.
fcomp_scan() being dumb. I have to alter it. Also a little bit in fcomp_push()
(I thought realloc(0, n) would be like malloc(n)).
BruteForce() needs to be altered a bit because of a compiler bug:
for (j = 0; blah blah; j++){ }
must become
for (j = 0; blah blah; ) { j++; }
For some odd reason. Debugging, it seems to infinitely loop here and
leave j as 0.
You know it would help if someone would grab GDB, grab the source,
and debug it! My head is starting to hurt....
Any takers?
--Bluefox Icy
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2003-04-27 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 22:32 CRAP it crashes rmoser
2003-04-27 23:20 ` rmoser [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=200304271920110140.02AAE835@smtp.comcast.net \
--to=mlmoser@comcast.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).