> > that sucker is on the stack. by-by no-execute stack. > > how does it get to the stack? is it just copied from > > the text segment or is it compiled at run time? > > > > I don't think I posted the whole code, so that's my bad. The X was on the > stack to begin with as the first X was an automatic variable in a function. > I'd be a little surprised to find an automatic variable in the text > segment, but perhaps that's just my not remembering things properly. > (didn't mean that tongue in cheek, I don't think about that stuff much > these days, as I've spent the last year or so doing Erlang and Haskell.)
it is the block itself that apple claims is on the stacp (your grand centeral reference, p. 38). and i wonder how it gets there. is it just copied from the text segment? that seems kind of pointless. why not just execute it from the text segment? or is it modified (compiled?) at run time? - erik
