Alex, I can debug my module as a stand alone application, but when I run my main application it does not stop at breakpoints in the module. Any idea?
Thanks On Wed, Aug 6, 2014 at 12:01 AM, Alex Harui <[email protected]> wrote: > > > On 8/5/14 6:02 PM, "mark goldin" <[email protected]> wrote: > > >Yes, that might be an issue. Here is how a project is structured. It has > >the main application file and a bunch of mxml files that are in fact > >modules. So, it's one single project with a number of modules. Can I > >specify whether each module is compiled with or without debugging info? > I think Flash Builder should be building them all as debug version if they > are all ending up in bin-debug. > > The second most common problem is that the classes you are trying to debug > were loaded before the module was loaded and the classes were not a debug > version. I would turn off the use of RSLs while debugging. > > Next most common problem is that the module gets unloaded because nothing > is keeping it in memory. The debugger may try to force GC more often and > kick the module out sooner. > > Another potential problem is that the module is old and doesn't match the > source code. > > You can try debugging with fdb. It will halt every time a debuggable > module loads. That's how I know a module was not built with debug info in > it. > > -Alex > > > > > > >On Tue, Aug 5, 2014 at 5:11 PM, Alex Harui <[email protected]> wrote: > > > >> Number one reason is that the modules are not compiled with the -debug > >> flag. > >> > >> Could that be your issue? > >> -Alex > >> > >> On 8/5/14 1:51 PM, "mark goldin" <[email protected]> wrote: > >> > >> >Is there any problem debugging an application that uses modules? I can > >>get > >> >into code when I run main file, but a break point in the module code > >>does > >> >not seem to stop execution. > >> > > >> >Thanks > >> > >> > >
