From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Thu, 12 May 2005 09:19:00 +0200
Bob Rogers wrote:
>
> I'm sorry, but I'm still seeing the same syndrome in r8070, segfaulting
> in the same place, though now for only a subset of *.pbc files . . .
Yet another uninitialized poin
Bob Rogers wrote:
I'm sorry, but I'm still seeing the same syndrome in r8070, segfaulting
in the same place, though now for only a subset of *.pbc files . . .
Yet another uninitialized pointer variable - fixed.
-- Bob
Thanks for reporting.
BTW could you/someone make a test for disassemble, to
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Wed, 04 May 2005 09:38:41 +0200
Bob Rogers wrote:
>. . . but I can't figure out why. I thought the patch below would
> help, but it appears that the value of c is itself broken somehow.
The memory handling was broken and disas
Bob Rogers wrote:
. . . but I can't figure out why. I thought the patch below would
help, but it appears that the value of c is itself broken somehow.
The memory handling was broken and disassemble didn't know how to handle
PMC constants.
Fixed - rev 7971.
Thanks for testing,
leo
Bob~
On 5/3/05, Bob Rogers <[EMAIL PROTECTED]> wrote:
>. . . but I can't figure out why. I thought the patch below would
> help, but it appears that the value of c is itself broken somehow.
>
> . . .
> This GDB was configured as "i586-suse-linux"...
> (gdb) r runtime/parrot/libra
. . . but I can't figure out why. I thought the patch below would
help, but it appears that the value of c is itself broken somehow.
. . .
This GDB was configured as "i586-suse-linux"...
(gdb) r runtime/parrot/library/config.pbc
Starting program: /usr/src/parrot/disassemble
ru
