On Wed, 21 Sep 2005, Joshua Hoblitt via RT wrote:
[EMAIL PROTECTED] - Fri Oct 31 12:58:45 2003]:
An attempt to build Parrot with PIO_OS_STDIO defined (as is the case
when you're trying to build miniparrot) dies in core_ops.c with the error
message:
ops/io.ops: In function `Parrot_sockad
On Wed, 21 Sep 2005, Joshua Hoblitt via RT wrote:
[EMAIL PROTECTED] - Tue May 27 19:30:39 2003]:
Currently, if you're in the debugger, and do anything that causes an
internal_exception call within the interpreter, you get a segfault.
[Backtrace snipped]
...etc
I think what's happen
On Wed, 2005-09-21 at 11:44 +0100, Jonathan Worthington wrote:
> >> but I can cause a segfault from random input on x86.
> >>
> >> --
> >> $ ./parrot -j docs/running.pod
> >> Segmentation fault
> This is a Bad Thing and needs fixing. I'll see what I can find - I don't
> even see a segfault or a
I've just closed the ticket. Thanks.
simon:
> >> > If you're going to check the magic after the wordsize and bytecode, you
> >> > might as well get rid of it altogether.
...
Jonathan:
> ...Change the packfile format, or code around the current way
If you do tweak the signature for the packfile format, I suggest you
take a leaf out of
Jonathan Worthington wrote:
> FORMAT PROPOSAL...
Great! Anything that brings parrot closer to being able to report the
HLL filename and line numbers is a good thing!
> SOURCE SEGMENTS
> ... the idea would seem to be
> that this segment can contain source code. I suspect the intention of it
>
Hi,
Since my last post about pbc_merge, I've also checked in some tests plus
hunted down and fixed a problem that prevented the tool from working in the
leo-ctx5 branch. I think this ticket can now be closed (I don't have RT
privs to do stuff like this).
Thanks,
Jonathan
"Joshua Hoblitt via RT" <[EMAIL PROTECTED]> wrote:
[jhoblitt - Mon Sep 19 22:28:00 2005]:
> [EMAIL PROTECTED] - Sun Sep 22 07:13:56 2002]:
>
> The point of having a validifiable magic number at the start
> of a bytecode file is to avoid this sort of thing:
>
> % ../../parrot -j mops.pasm
> Pack
I'm pretty sure all the stuff i added (plus more) is now there thanks
to someone else. They may have started from my code, they may not
have. Haven't really looked at the project since.
Peter
On 21/09/2005, at 2:20 PM, Joshua Hoblitt via RT wrote:
[EMAIL PROTECTED] - Tue May 06 06:39:11 20
