, August 5, 2013 3:09:50 PM GMT -05:00 US/Canada Eastern
Subject: Re: [racket-dev] Too many struct definitions leads to literal
local-code error
Seeing #local-code is about the same as a seg fault.
Can you send me something to replicate the crash on my machine?
On Aug 5, 2013, at 11:55 AM
: [racket-dev] Too many struct definitions leads to literal
local-code error
Thanks --- I've pushed a repair, finally.
Unless I'm confused, the problem was a bug in the bytecode format that
has been around since v300 or so.
At Mon, 5 Aug 2013 15:20:17 -0400 (EDT), J. Ian Johnson wrote:
Pushed current
I'm working more on my analysis framework, and added many different kinds of
new continuation frames. I get to a point where I comment out all definitions
past a certain point (and their uses) and the program
compiles. I add one more (any one) and I get the following error:
...@ccs.neu.edu
To: dev dev@racket-lang.org
Sent: Monday, August 5, 2013 2:55:01 PM GMT -05:00 US/Canada Eastern
Subject: [racket-dev] Too many struct definitions leads to literal
local-code error
I'm working more on my analysis framework, and added many different kinds of
new continuation frames. I get
Seeing #local-code is about the same as a seg fault.
Can you send me something to replicate the crash on my machine?
On Aug 5, 2013, at 11:55 AM, J. Ian Johnson i...@ccs.neu.edu wrote:
I'm working more on my analysis framework, and added many different kinds of
new continuation frames. I
. Ian Johnson i...@ccs.neu.edu
Cc: dev dev@racket-lang.org
Sent: Monday, August 5, 2013 3:09:50 PM GMT -05:00 US/Canada Eastern
Subject: Re: [racket-dev] Too many struct definitions leads to literal
local-code error
Seeing #local-code is about the same as a seg fault.
Can you send me something
6 matches
Mail list logo
