On 3/18/16, 5:33 AM, "lexx" <[email protected]> wrote:
>Hi All, > >As far as I understand, fdb doesn't support p-code level debugging (i.e. >step by step evaluation of p-code, without sources attached) at the >moment. >I wonder, how much effort would I need to implement this myself? If this >goal is feasible, can someone please point out a place to start in the >code? >Thanks in advance! I'm not an expert on the debugger, but I think it doesn't rely on source code as much as it relies on debugfile and debugline ABC codes in the SWF itself. To test that, you could build a SWC with -debug=true, use it in an app, move all the source files for the SWC somewhere else, and I'm pretty sure you can still set breakpoints if you know the name of the file and a line number that matches debugfile and debugline ABC codes in the SWF and the debugger stop at them and step, but I think it just won't show you any source. It isn't clear to me that the debugger/player knows how to work together to show you the ABC code, but I suppose you could dump the SWF and get the codes that match the debugfile/debugline and display that if there aren't any sources. And, I suppose you could further write some code that grabs any SWF without debugfile/debugline ABC codes and insert your own debugfile/debugline after each ABC code so you could then step at each ABC code. HTH, -Alex
