Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Bug: segfault in imcc parsing bad if statement
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  6 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Gopal V  
View profile  
 More options Nov 12 2004, 1:16 pm
Newsgroups: perl.perl6.internals
From: parrotbug-follo...@parrotcode.org (Gopal V)
Date: Fri, 12 Nov 2004 10:16:31 -0800
Local: Fri, Nov 12 2004 1:16 pm
Subject: [perl #32421] Bug: segfault in imcc parsing bad if statement
# New Ticket Created by  Gopal V
# Please include the string:  [perl #32421]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=32421 >

The following code segfaults with parrot poicephalus

.sub _MAIN
    $I0=1
    if$I0 < 2  goto LBL1
LBL1:
    end
    ret
.end

Fix at your leisure :)

__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Matt Diephouse  
View profile  
 More options Nov 12 2004, 4:59 pm
Newsgroups: perl.perl6.internals
From: mdd...@gmail.com (Matt Diephouse)
Date: Fri, 12 Nov 2004 16:59:02 -0500
Local: Fri, Nov 12 2004 4:59 pm
Subject: Re: [perl #32421] Bug: segfault in imcc parsing bad if statement
On Fri, 12 Nov 2004 10:16:31 -0800, via RT Gopal V

The code works if you put a space between "if" and "$I0":

 .sub _MAIN
    $I0=1
    if $I0 < 2 goto LBL1
 LBL1:
    end
    ret
 .end

--
matt diephouse
http://matt.diephouse.com


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Dan Sugalski  
View profile  
 More options Nov 12 2004, 5:05 pm
Newsgroups: perl.perl6.internals
From: d...@sidhe.org (Dan Sugalski)
Date: Fri, 12 Nov 2004 17:05:44 -0500
Local: Fri, Nov 12 2004 5:05 pm
Subject: Re: [perl #32421] Bug: segfault in imcc parsing bad if statement
At 4:59 PM -0500 11/12/04, Matt Diephouse wrote:

Right, but the pir parser shouldn't segfault on bad input.
--
                                Dan

--------------------------------------it's like this-------------------
Dan Sugalski                          even samurai
d...@sidhe.org                         have teddy bears and even
                                       teddy bears get drunk


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Leopold Toetsch  
View profile  
 More options Nov 12 2004, 5:07 pm
Newsgroups: perl.perl6.internals
From: l...@toetsch.at (Leopold Toetsch)
Date: Fri, 12 Nov 2004 23:07:36 +0100
Local: Fri, Nov 12 2004 5:07 pm
Subject: Re: [perl #32421] Bug: segfault in imcc parsing bad if statement
[This message has also been posted.]

Gopal V <parrotbug-follo...@parrotcode.org> wrote:
> # New Ticket Created by  Gopal V
> # Please include the string:  [perl #32421]
> # in the subject line of all future correspondence about this issue.
> # <URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=32421 >
> The following code segfaults with parrot poicephalus
> .sub _MAIN
>     $I0=1
>     if$I0 < 2  goto LBL1

      ^^^^^

Segfault in the lexer. Bad.

349                 sprintf(label, "%s%d", yytext, frames->label);
(gdb) p frames
$1 = (struct macro_frame_t *) 0x0

leo


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Gopal V  
View profile  
 More options Nov 13 2004, 8:23 am
Newsgroups: perl.perl6.internals
From: gopal...@yahoo.com (Gopal V)
Date: Sat, 13 Nov 2004 05:23:33 -0800 (PST)
Local: Sat, Nov 13 2004 8:23 am
Subject: Re: [perl #32421] Bug: segfault in imcc parsing bad if statement

> Segfault in the lexer. Bad.

> 349                 sprintf(label, "%s%d", yytext,
> frames->label);
> (gdb) p frames
> $1 = (struct macro_frame_t *) 0x0

I didn't know how or why or what a frame is in this
context which is why this isn't a patch :)

__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Leopold Toetsch  
View profile  
 More options Nov 16 2004, 3:55 am
Newsgroups: perl.perl6.internals
From: l...@toetsch.at (Leopold Toetsch)
Date: Tue, 16 Nov 2004 09:55:00 +0100
Subject: Re: [perl #32421] Bug: segfault in imcc parsing bad if statement

Gopal V <gopal...@yahoo.com> wrote:
>> Segfault in the lexer. Bad.

>> 349                 sprintf(label, "%s%d", yytext,
>> frames->label);
>> (gdb) p frames
>> $1 = (struct macro_frame_t *) 0x0
> I didn't know how or why or what a frame is in this
> context which is why this isn't a patch :)

No problem. The syntax {ID}$ is used internally during the expansion of
local labels inside macros, which happen to be accumulated in frame
structures.

Fixed.

Thanks for reporting,
leo


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2010 Google