On Wed, Apr 13, 2005 at 05:42:20PM -0500, Pete Harlan wrote:
> On Tue, Apr 12, 2005 at 06:05:18PM -0400, Lennart Sorensen wrote:
> ...
> > If you fix this bug, it seems to run perfectly all the way through:
> >
> > tex.c line 95:
> > Was: memset(zbuff, 0x55, (X_s * Y_s * sizeof(long)));
> > Should
On Tue, Apr 12, 2005 at 06:05:18PM -0400, Lennart Sorensen wrote:
...
> If you fix this bug, it seems to run perfectly all the way through:
>
> tex.c line 95:
> Was: memset(zbuff, 0x55, (X_s * Y_s * sizeof(long)));
> Should be: memset(zbuff, 0x55, (X_s * Y_s * sizeof(int)));
>
> Len Sorensen
[Ni
On Wed, Apr 13, 2005 at 12:45:38AM +0200, Ernest jw ter Kuile wrote:
> On Tuesday 12 April 2005 23:25, Ernest jw ter Kuile wrote:
> > Confirm. Although I got so mesmerised by the images that I forgot to time
> > it.
> >
> > > 6. After 3 minutes 47 seconds (+/- a couple seconds) bb segfaults. It
> >
On Tue, Apr 12, 2005 at 08:41:07PM -0700, Corey Hickey wrote:
> Thank you for the fix! That was more than I expected. Also, thank you to
> the others for confirming this.
It shows up as a segfault in loading images with sound off, but it shows
up as an attempt to write outside allocated memory wit
Ernest jw ter Kuile wrote:
> On Tuesday 12 April 2005 23:25, Ernest jw ter Kuile wrote:
>
>>Confirm. Although I got so mesmerised by the images that I forgot to time
>>it.
>>
>>
>>>6. After 3 minutes 47 seconds (+/- a couple seconds) bb segfaults. It
>>>happens right before the section with the to
Lennart Sorensen wrote:
>
> Turns out it is a memory wipe caused elsewhere in the program as far as
> I can tell.
>
> If you fix this bug, it seems to run perfectly all the way through:
>
> tex.c line 95:
> Was: memset(zbuff, 0x55, (X_s * Y_s * sizeof(long)));
> Should be: memset(zbuff, 0x55, (X
On Tuesday 12 April 2005 23:25, Ernest jw ter Kuile wrote:
> Confirm. Although I got so mesmerised by the images that I forgot to time
> it.
>
> > 6. After 3 minutes 47 seconds (+/- a couple seconds) bb segfaults. It
> > happens right before the section with the toroid.
hmmm, actually here it goes
On Tue, Apr 12, 2005 at 05:43:19PM -0400, Lennart Sorensen wrote:
> On Tue, Apr 12, 2005 at 05:14:09PM -0400, Lennart Sorensen wrote:
> > Yes I get a segfault running with the default options here too.
> >
> > Maybe I will investigate... :)
>
> Well here is what gdb returns:
>
> Program received
On Tue, Apr 12, 2005 at 05:14:09PM -0400, Lennart Sorensen wrote:
> Yes I get a segfault running with the default options here too.
>
> Maybe I will investigate... :)
Well here is what gdb returns:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912510027664 (LWP 2427
On Tuesday 12 April 2005 23:01, Corey Hickey wrote:
> bb (the aalib demo) is reproducably segfaulting for me when I run the
> amd64 build; the i386 build works fine in my chroot. I'm planning to
> report the bug, but I was hoping someone here could confirm that it
> happens to them too.
Confirm. A
On Tue, Apr 12, 2005 at 02:01:31PM -0700, Corey Hickey wrote:
> bb (the aalib demo) is reproducably segfaulting for me when I run the
> amd64 build; the i386 build works fine in my chroot. I'm planning to
> report the bug, but I was hoping someone here could confirm that it
> happens to them too.
>
On Tue, Apr 12, 2005 at 02:01:31PM -0700, Corey Hickey wrote:
> bb (the aalib demo) is reproducably segfaulting for me when I run the
> amd64 build; the i386 build works fine in my chroot. I'm planning to
> report the bug, but I was hoping someone here could confirm that it
> happens to them too.
bb (the aalib demo) is reproducably segfaulting for me when I run the
amd64 build; the i386 build works fine in my chroot. I'm planning to
report the bug, but I was hoping someone here could confirm that it
happens to them too.
Hardware:
Athlon64 3400+
DFI Lanparty nf3 250gb
Sound Blaster Live
13 matches
Mail list logo
