Just so everyone knows, I think I've found the problem. The debugging
in the default compile was throwing us all off. The error was happening
on the following line:
unsigned long ETA=(unsigned long)((TotalBytes-CurrentBytes)/CurrentCPS);
If you stare at this, you'll realize that CurrentCP
On Sun, Feb 17, 2002 at 09:22:49AM -0500, Daniel Burrows <[EMAIL PROTECTED]>
was heard to say:
> On Thu, Nov 01, 2001 at 11:00:51PM +0100, Falk Hueffner <[EMAIL PROTECTED]>
> was heard to say:
> > > Can anyone reproduce/hunt down 114270? I can't reproduce it (I think
> > > it's probably Alpha
On Thu, Nov 01, 2001 at 11:00:51PM +0100, Falk Hueffner <[EMAIL PROTECTED]> was
heard to say:
> > Can anyone reproduce/hunt down 114270? I can't reproduce it (I think
> > it's probably Alpha specific), and I don't really have much of an
> > idea where it could be. I haven't gotten any other re
Actually, I don't think I can effectively come up with a patch for
this. (the infinite loop) I don't even know what area of code to look
at, and I can't debug on a live system since I have no alpha.
Would it be possible for someone on alpha to find out what's going on
and send me either a pa
Goswin Brederlow wrote:
>
> [EMAIL PROTECTED]:~% cat foo.cc
> #include
> #include
>
> int main() {
> double d = 1.0 + sqrt(-1.0);
> }
> [EMAIL PROTECTED]:~% g++ -o foo foo.cc
> [EMAIL PROTECTED]:~% ./foo
> zsh: floating point exception ./foo
> [EMAIL PROTECTED]:~
Goswin Brederlow wrote:
> "Donsbach, Jeff" <[EMAIL PROTECTED]> writes:
>
>
>>98 times out of 100, Floating Point Exception errors on Alpha are caused
>>by either an uninitialized floating point variable (that happens to have
>>random garbage in it) being used in a calculation, or a floating point
>
"Donsbach, Jeff" <[EMAIL PROTECTED]> writes:
> 98 times out of 100, Floating Point Exception errors on Alpha are caused
> by either an uninitialized floating point variable (that happens to have
> random garbage in it) being used in a calculation, or a floating point
> "divide by zero" operation.
g
> Subject: Re: aptitude on alpha (again, sigh)
>
>
> On Thu, Nov 01, 2001 at 04:03:29PM -0500, Daniel Burrows wrote:
> > On Thu, Nov 01, 2001 at 03:43:51PM -0500, "Christopher C.
> Chimelis" <[EMAIL PROTECTED]> was heard to say:
> > >
> > &g
On Thu, Nov 01, 2001 at 04:03:29PM -0500, Daniel Burrows wrote:
> On Thu, Nov 01, 2001 at 03:43:51PM -0500, "Christopher C. Chimelis" <[EMAIL
> PROTECTED]> was heard to say:
> >
> > It's an Alpha thing. I started looking into this bug a few weeks ago, but
> > got busy with other things. One thi
Christopher C. Chimelis wrote:
On Thu, 1 Nov 2001, Daniel Burrows wrote:
Can anyone reproduce/hunt down 114270? I can't reproduce it (I think
it's probably Alpha specific), and I don't really have much of an idea
where it could be. I haven't gotten any other reports of this, which
makes me wonde
On Thu, Nov 01, 2001 at 11:00:51PM +0100, Falk Hueffner <[EMAIL PROTECTED]> was
heard to say:
> Daniel Burrows <[EMAIL PROTECTED]> writes:
>
> > Can anyone reproduce/hunt down 114270? I can't reproduce it (I think
> > it's probably Alpha specific), and I don't really have much of an
> > idea w
Daniel Burrows <[EMAIL PROTECTED]> writes:
> Can anyone reproduce/hunt down 114270? I can't reproduce it (I think
> it's probably Alpha specific), and I don't really have much of an
> idea where it could be. I haven't gotten any other reports of this,
> which makes me wonder if maybe it could
On Thu, 1 Nov 2001, Daniel Burrows wrote:
> Why does this fix the problem? (ie, is this just working around a bug
> in the code?) The documentation says it has something to do with
> floating-point comparisons being "inexact". Specifically, it mentions
> handling NaN and +-Inf correctly. Th
On Thu, Nov 01, 2001 at 03:43:51PM -0500, "Christopher C. Chimelis" <[EMAIL
PROTECTED]> was heard to say:
>
> > Can anyone reproduce/hunt down 114270? I can't reproduce it (I think
> > it's probably Alpha specific), and I don't really have much of an idea
> > where it could be. I haven't gott
On Thu, 1 Nov 2001, Daniel Burrows wrote:
> Can anyone reproduce/hunt down 114270? I can't reproduce it (I think
> it's probably Alpha specific), and I don't really have much of an idea
> where it could be. I haven't gotten any other reports of this, which
> makes me wonder if maybe it could
15 matches
Mail list logo
