search for: parsestatementtable

...at was mostly laziness on my part, hoping that you had a plan that you could just spell out for me. Having overcome my laziness a bit today and looked at the code some more, it looks like I'd need to pass the new map (however it was stored) into DWARFDebugLine and have that class use it in its parseStatementTable and associated methods. It looks like it would take a bit of thought to figure out which fields might be candidates for relocation and which wouldn't, but I suppose that's manageable. Does this sound basically correct? Or should I just wait for you to do the work? :) -Andy From: Eric...

...t you > could just spell out for me.**** > > ** > Oh sorry :) > ** > > Having overcome my laziness a bit today and looked at the code some more, > it looks like I’d need to pass the new map (however it was stored) into > DWARFDebugLine and have that class use it in its parseStatementTable and > associated methods. It looks like it would take a bit of thought to figure > out which fields might be candidates for relocation and which wouldn’t, but > I suppose that’s manageable.**** > > ** ** > > Does this sound basically correct? Or should I just wait for you to...

On Thu, Jan 10, 2013 at 3:13 PM, Kaylor, Andrew <andrew.kaylor at intel.com>wrote: > Actually, MCJIT doesn’t perform relocations on debug sections. I’m not > sure that would matter anyway. The place where I’m handling the debug > information is outside MCJIT and the MCJIT relocation code isn’t really > accessible at that point.**** > > ** > I know it doesn't,

Actually, MCJIT doesn't perform relocations on debug sections. I'm not sure that would matter anyway. The place where I'm handling the debug information is outside MCJIT and the MCJIT relocation code isn't really accessible at that point. Right now, when MCJIT emits an object image, it broadcasts an event to any registered listeners indicating that an object was emitted, passing