The parrot-nqp.c file is generated by the pbc_to_exe program, which contains the source lines referenced here. The source for pbc_to_exe is in tools/dev/ .
HTH, Pm On Sat, Jun 01, 2013 at 12:46:46PM -0500, Jonathan "Duke" Leto wrote: > Howdy, > > I think my GSoC student has possibly found a bug in parrot-nqp. I > won't have much time during YAPC::NA to help him. > > Could anybody step in and help him debug this issue? > > Duke > > > ---------- Forwarded message ---------- > From: Saurabh Kumar <saurabhgee...@gmail.com> > Date: Sat, Jun 1, 2013 at 11:55 AM > Subject: Re: [Passed] letolabs/parrot-libgit2#21 (nciupdate - 4d61364) > To: Jonathan Duke Leto <jonat...@leto.net> > > > On Sat, Jun 1, 2013 at 8:12 PM, Jonathan "Duke" Leto <jonat...@leto.net> > wrote: > > Howdy, > > > > Can you show me where (a link to Github is most useful) where you > > think the NQP exit code bug is? > > > > Thanks! > > Ah, sorry, I was looking at parrot-nqp.c, which seems to be a > generated file, and not in the parrot.git repository. The main > function in the C file (Around line 37296) seems to have 7 locations > where it can exit. Before the program exits successfully, this is the > only location that should give off an error: > > if (!Parrot_api_run_bytecode(interp, pbc, argsarray)) { > show_last_error_and_exit(interp); > } > > Apparently this doesn't show a error. I'm not sure which source file > generates this C file now. I will look into it. > > > -- > Jonathan "Duke" Leto <jonat...@leto.net> > Leto Labs LLC http://letolabs.com > 209.691.DUKE http://duke.leto.net > @dukeleto _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev