[racket-dev] "Too many" struct definitions leads to literal <local-code> error

Many thanks. First call-with-values/begin0 and now this. I should be the deeeeep bug finder, heh.
-Ian
----- Original Message -----
From: Matthew Flatt <mflatt at cs.utah.edu>
To: J. Ian Johnson <ianj at ccs.neu.edu>
Cc: dev <dev at racket-lang.org>
Sent: Wed, 7 Aug 2013 11:43:12 -0400 (EDT)
Subject: Re: [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 branch to
> https://github.com/dvanhorn/oaam/tree/thocon
> 
> kcfa.rkt has an "mflatt" comment that will point you at the problem lines of 
> code.
> 
> The entry point for the project is kcfa-instanstantiations.rkt
> -Ian
> ----- Original Message -----
> From: "Matthew Flatt" <mflatt at cs.utah.edu>
> To: "J. Ian Johnson" <ianj at ccs.neu.edu>
> Cc: "dev" <dev at 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 to replicate the crash on my machine?
> 
> 
> 
> On Aug 5, 2013, at 11:55 AM, "J. Ian Johnson" <ianj at ccs.neu.edu> wrote:
> 
> > 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:
> > 
> > kcfa-instantiations.rkt:136:6: ?: literal data is not allowed;
> > no #%datum syntax transformer is bound
> >  in: #<local-code>
> >  context...:
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:234:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:181:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:234:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:181:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:234:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:181:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:234:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:181:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:234:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:181:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:234:0
> >   /home/ianj/racket/racket/collects/racket/splicing.rkt:181:0
> >   /home/ianj/racket/racket/collects/racket/private/modbeg.rkt:46:4
> >   /home/ianj/racket/racket/collects/compiler/cm.rkt:345:0: compile-zo*
> >   /home/ianj/racket/racket/collects/compiler/cm.rkt:552:26
> >   /home/ianj/racket/racket/collects/compiler/cm.rkt:545:42...
> > 
> > This is blocking progress. I'm about to pull and hope for the best. Any ideas 
> what might be causing this kind of behavior in the expander?
> > -Ian
> > _________________________
> >  Racket Developers list:
> >  http://lists.racket-lang.org/dev
> >