HI Fred, Welcomed advice. Will see where it takes me. It looks like it's a hit-or-try-again approach. I'll give it a try on how far Byebug takes me.
I've will also see how Dtrace might be used on my Mac. I have done some experimenting with it on my Sun system a few years ago tracing c++ code etc I appreciate your directions to take. Dave On Monday, November 30, 2015 at 8:28:14 AM UTC-5, Frederick Cheung wrote: > > > On Sunday, November 29, 2015 at 4:09:04 PM UTC, dave wrote: >> >> Fred >>> >> >> Hi Fred, >> Thank you for your response and explanation: development vs production >> javascript tags. Yes I also set traces into sprockets and manifest.rb code >> before my original post. >> Where the tracing falls down is in the eval statement which switches into >> another run context and so Byebug is left hanging. >> Maybe this is a Byebug forum question? or possibly i'm pushing its >> run-context envelope past its original design? >> >>> >>> > Given that the eval calls Rack::Builder.new I would set a breakpoint on > Rack::Builder.initialize. I don't think you need any tools beyond bye bug > for this sort of thing. However, this won't lead you directly to where > javascript gets generated because that is done on demand, not at app > startup. You'd want a breakpoint at the top of the rack middleware if you > wanted to trace what happens when a js file is requested. > > Fred > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/0539c761-74e6-4191-aad9-bd0407e68e53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
