On 2/6/16, 9:09 AM, "lexx" <[email protected]> wrote:
> >Can it be the case that some classes have debug info, while others don't? > I think so. If you link in code from a SWC that did not have debug info in it, then it might be that those classes will not be listed in "info files". Also, keep in mind that "info files" is not always in alphabetical order, so make sure you scan the entire list. If you can see the <doABC2> tag in SWFDump, use the -abc option to see all the code and you should see that in classes that do show up in "info files" there are "debugfile" and "debugline" opcodes, and maybe for the class you are interested in, those opcodes aren't there. > >Alex Harui wrote >> When you see [DYNAMIC] it means that SWFs are being loaded (often as >>RSLs) >> so you don't really have a single-swf app. If the classes you are >>looking >> for are in those SWFs then that would explain what you are seeing. > >Is there any way to get URLs/paths for this dynamically loaded SWF/RSLs? I >couldn't find any references in code, SWF or application.xml. The only >idea >I have right now is to add some debug output to fdb itself to see what it >loads and where from. Well, RSLs should get loaded from a central place in the code. And the systemManager.info() structure should have the list of RSLs loaded by the Flex RSL subsystem. If you are using some other framework then you might have to find its central point. Other SWFs can be loaded by SWFLoader. And then, there's always the chance that some custom code is going to load a SWF. But usually, setting a breakpoint on SWFLoader and RSLListLoader will help you find the things getting loaded. > >Thanks again for your time and help! > >PS: Sorry for elementary questions. I'm a Java dev, and all that AS stuff >is >new to me. Welcome to Flex! -Alex
