Debugging application with modules

[mark goldin <ma...@gmail.com>]

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

Re: Debugging application with modules

[Alex Harui <ah...@adobe.com>]

If the first app is debuggable, you will be out of luck.  The first
debuggable SWF needs to be the app that loads the modules or the module
itself, and RSLs and other subordinate SWFs may get loaded first and end
up being the thing that gets debugged.  I think the FB console shows the
list of SWFs being loaded.

-Alex

On 8/7/14 9:13 AM, "mark goldin" <ma...@gmail.com> wrote:

>I was also able to load a new app file into the same window but still no
>debugging.
>
>
>On Thu, Aug 7, 2014 at 10:40 AM, mark goldin <ma...@gmail.com>
>wrote:
>
>> < If you export the main app for release and run that
>> How exactly would I run it? Directly from the browser? How then a
>> debugging session is going to start?
>>
>>
>> On Thu, Aug 7, 2014 at 10:30 AM, Alex Harui <ah...@adobe.com> wrote:
>>
>>>
>>>
>>> On 8/7/14 4:34 AM, "mark goldin" <ma...@gmail.com> wrote:
>>>
>>> >Seems like I got confused. Here is how it works.
>>> >The main app fires another app file into a new browser window and that
>>> new
>>> >app is not debugging and I think because this is a new FP session
>>>that a
>>> >current debugging session knows nothing about. So, with this setup is
>>>it
>>> >possible to get a new browser window debugged?
>>> Probably.  The debugger hooks to the first debuggable SWF that gets
>>>loaded
>>> after it starts.  If you export the main app for release and run that,
>>>it
>>> shouldn't have any debug info.  You may need to turn off RSLs if you
>>>are
>>> using them.  Then if the next debuggable SWF that loads is the app
>>>file in
>>> the new browser window, it should hook up correctly.
>>>
>>> -Alex
>>>
>>> >
>>> >Thanks
>>> >
>>> >
>>> >On Wed, Aug 6, 2014 at 11:16 PM, Alex Harui <ah...@adobe.com> wrote:
>>> >
>>> >> Modules usually aren't stand along applications.  Maybe there is
>>> >>something
>>> >> unusual about your setup.
>>> >>
>>> >> If the main app is not set up for debug and includes classes you
>>>think
>>> >>are
>>> >> in the module, that would block debugging of the module.
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 8/6/14 10:35 AM, "mark goldin" <ma...@gmail.com> wrote:
>>> >>
>>> >> >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 <ah...@adobe.com>
>>>wrote:
>>> >> >
>>> >> >>
>>> >> >>
>>> >> >> On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com>
>>> 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" <ma...@gmail.com>
>>>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
>>> >> >> >>
>>> >> >> >>
>>> >> >>
>>> >> >>
>>> >>
>>> >>
>>>
>>>
>>

Re: Debugging application with modules

[mark goldin <ma...@gmail.com>]

I was also able to load a new app file into the same window but still no
debugging.


On Thu, Aug 7, 2014 at 10:40 AM, mark goldin <ma...@gmail.com> wrote:

> < If you export the main app for release and run that
> How exactly would I run it? Directly from the browser? How then a
> debugging session is going to start?
>
>
> On Thu, Aug 7, 2014 at 10:30 AM, Alex Harui <ah...@adobe.com> wrote:
>
>>
>>
>> On 8/7/14 4:34 AM, "mark goldin" <ma...@gmail.com> wrote:
>>
>> >Seems like I got confused. Here is how it works.
>> >The main app fires another app file into a new browser window and that
>> new
>> >app is not debugging and I think because this is a new FP session that a
>> >current debugging session knows nothing about. So, with this setup is it
>> >possible to get a new browser window debugged?
>> Probably.  The debugger hooks to the first debuggable SWF that gets loaded
>> after it starts.  If you export the main app for release and run that, it
>> shouldn't have any debug info.  You may need to turn off RSLs if you are
>> using them.  Then if the next debuggable SWF that loads is the app file in
>> the new browser window, it should hook up correctly.
>>
>> -Alex
>>
>> >
>> >Thanks
>> >
>> >
>> >On Wed, Aug 6, 2014 at 11:16 PM, Alex Harui <ah...@adobe.com> wrote:
>> >
>> >> Modules usually aren't stand along applications.  Maybe there is
>> >>something
>> >> unusual about your setup.
>> >>
>> >> If the main app is not set up for debug and includes classes you think
>> >>are
>> >> in the module, that would block debugging of the module.
>> >>
>> >> -Alex
>> >>
>> >> On 8/6/14 10:35 AM, "mark goldin" <ma...@gmail.com> wrote:
>> >>
>> >> >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 <ah...@adobe.com> wrote:
>> >> >
>> >> >>
>> >> >>
>> >> >> On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com>
>> 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" <ma...@gmail.com> 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
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>
>

Re: Debugging application with modules

[Alex Harui <ah...@adobe.com>]

There are various tricks to try.  I don't use FB for debugging complex
scenarios, I use FDB instead.  But I believe some folks create a custom
debug config that launches a release SWF, or maybe they manually copy the
release SWF over the debug SWF.

-Alex

On 8/7/14 8:40 AM, "mark goldin" <ma...@gmail.com> wrote:

>< If you export the main app for release and run that
>How exactly would I run it? Directly from the browser? How then a
>debugging
>session is going to start?
>
>
>On Thu, Aug 7, 2014 at 10:30 AM, Alex Harui <ah...@adobe.com> wrote:
>
>>
>>
>> On 8/7/14 4:34 AM, "mark goldin" <ma...@gmail.com> wrote:
>>
>> >Seems like I got confused. Here is how it works.
>> >The main app fires another app file into a new browser window and that
>>new
>> >app is not debugging and I think because this is a new FP session that
>>a
>> >current debugging session knows nothing about. So, with this setup is
>>it
>> >possible to get a new browser window debugged?
>> Probably.  The debugger hooks to the first debuggable SWF that gets
>>loaded
>> after it starts.  If you export the main app for release and run that,
>>it
>> shouldn't have any debug info.  You may need to turn off RSLs if you are
>> using them.  Then if the next debuggable SWF that loads is the app file
>>in
>> the new browser window, it should hook up correctly.
>>
>> -Alex
>>
>> >
>> >Thanks
>> >
>> >
>> >On Wed, Aug 6, 2014 at 11:16 PM, Alex Harui <ah...@adobe.com> wrote:
>> >
>> >> Modules usually aren't stand along applications.  Maybe there is
>> >>something
>> >> unusual about your setup.
>> >>
>> >> If the main app is not set up for debug and includes classes you
>>think
>> >>are
>> >> in the module, that would block debugging of the module.
>> >>
>> >> -Alex
>> >>
>> >> On 8/6/14 10:35 AM, "mark goldin" <ma...@gmail.com> wrote:
>> >>
>> >> >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 <ah...@adobe.com>
>>wrote:
>> >> >
>> >> >>
>> >> >>
>> >> >> On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com>
>> 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" <ma...@gmail.com> 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
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>

Re: Debugging application with modules

[mark goldin <ma...@gmail.com>]

< If you export the main app for release and run that
How exactly would I run it? Directly from the browser? How then a debugging
session is going to start?


On Thu, Aug 7, 2014 at 10:30 AM, Alex Harui <ah...@adobe.com> wrote:

>
>
> On 8/7/14 4:34 AM, "mark goldin" <ma...@gmail.com> wrote:
>
> >Seems like I got confused. Here is how it works.
> >The main app fires another app file into a new browser window and that new
> >app is not debugging and I think because this is a new FP session that a
> >current debugging session knows nothing about. So, with this setup is it
> >possible to get a new browser window debugged?
> Probably.  The debugger hooks to the first debuggable SWF that gets loaded
> after it starts.  If you export the main app for release and run that, it
> shouldn't have any debug info.  You may need to turn off RSLs if you are
> using them.  Then if the next debuggable SWF that loads is the app file in
> the new browser window, it should hook up correctly.
>
> -Alex
>
> >
> >Thanks
> >
> >
> >On Wed, Aug 6, 2014 at 11:16 PM, Alex Harui <ah...@adobe.com> wrote:
> >
> >> Modules usually aren't stand along applications.  Maybe there is
> >>something
> >> unusual about your setup.
> >>
> >> If the main app is not set up for debug and includes classes you think
> >>are
> >> in the module, that would block debugging of the module.
> >>
> >> -Alex
> >>
> >> On 8/6/14 10:35 AM, "mark goldin" <ma...@gmail.com> wrote:
> >>
> >> >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 <ah...@adobe.com> wrote:
> >> >
> >> >>
> >> >>
> >> >> On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com>
> 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" <ma...@gmail.com> 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
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >>
> >>
>
>

Re: Debugging application with modules

[Alex Harui <ah...@adobe.com>]

On 8/7/14 4:34 AM, "mark goldin" <ma...@gmail.com> wrote:

>Seems like I got confused. Here is how it works.
>The main app fires another app file into a new browser window and that new
>app is not debugging and I think because this is a new FP session that a
>current debugging session knows nothing about. So, with this setup is it
>possible to get a new browser window debugged?
Probably.  The debugger hooks to the first debuggable SWF that gets loaded
after it starts.  If you export the main app for release and run that, it
shouldn't have any debug info.  You may need to turn off RSLs if you are
using them.  Then if the next debuggable SWF that loads is the app file in
the new browser window, it should hook up correctly.

-Alex

>
>Thanks
>
>
>On Wed, Aug 6, 2014 at 11:16 PM, Alex Harui <ah...@adobe.com> wrote:
>
>> Modules usually aren't stand along applications.  Maybe there is
>>something
>> unusual about your setup.
>>
>> If the main app is not set up for debug and includes classes you think
>>are
>> in the module, that would block debugging of the module.
>>
>> -Alex
>>
>> On 8/6/14 10:35 AM, "mark goldin" <ma...@gmail.com> wrote:
>>
>> >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 <ah...@adobe.com> wrote:
>> >
>> >>
>> >>
>> >> On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com> 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" <ma...@gmail.com> 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
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>

Re: Debugging application with modules

[mark goldin <ma...@gmail.com>]

Seems like I got confused. Here is how it works.
The main app fires another app file into a new browser window and that new
app is not debugging and I think because this is a new FP session that a
current debugging session knows nothing about. So, with this setup is it
possible to get a new browser window debugged?

Thanks


On Wed, Aug 6, 2014 at 11:16 PM, Alex Harui <ah...@adobe.com> wrote:

> Modules usually aren't stand along applications.  Maybe there is something
> unusual about your setup.
>
> If the main app is not set up for debug and includes classes you think are
> in the module, that would block debugging of the module.
>
> -Alex
>
> On 8/6/14 10:35 AM, "mark goldin" <ma...@gmail.com> wrote:
>
> >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 <ah...@adobe.com> wrote:
> >
> >>
> >>
> >> On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com> 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" <ma...@gmail.com> 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
> >> >>
> >> >>
> >>
> >>
>
>

Re: Debugging application with modules

[Alex Harui <ah...@adobe.com>]

Modules usually aren't stand along applications.  Maybe there is something
unusual about your setup.

If the main app is not set up for debug and includes classes you think are
in the module, that would block debugging of the module.

-Alex

On 8/6/14 10:35 AM, "mark goldin" <ma...@gmail.com> wrote:

>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 <ah...@adobe.com> wrote:
>
>>
>>
>> On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com> 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" <ma...@gmail.com> 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
>> >>
>> >>
>>
>>

Re: Debugging application with modules

[mark goldin <ma...@gmail.com>]

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 <ah...@adobe.com> wrote:

>
>
> On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com> 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" <ma...@gmail.com> 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
> >>
> >>
>
>

RE: Debugging application with modules

[Frédéric THOMAS <we...@hotmail.com>]

FDB (Flash / Flex debugger): http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7ffb.html
To use it with AIR apps, first start fdb, then type "run" and start another command line in which you launch your AIR app via ADL (don't forget to compile your AIR app / libs with debug=true), fdb will trigger you AIR launch and you'll be able to debug it.

Frédéric THOMAS

> Date: Wed, 6 Aug 2014 06:24:06 -0500
> Subject: Re: Debugging application with modules
> From: markzolotoy@gmail.com
> To: users@flex.apache.org
> 
> Thanks a lot Alex for such a detail info. One thing though, what's fdb?
> 
> 
> On Wed, Aug 6, 2014 at 12:01 AM, Alex Harui <ah...@adobe.com> wrote:
> 
> >
> >
> > On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com> 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" <ma...@gmail.com> 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
> > >>
> > >>
> >
> >
 		 	   		  

Re: Debugging application with modules

[mark goldin <ma...@gmail.com>]

Thanks a lot Alex for such a detail info. One thing though, what's fdb?


On Wed, Aug 6, 2014 at 12:01 AM, Alex Harui <ah...@adobe.com> wrote:

>
>
> On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com> 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" <ma...@gmail.com> 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
> >>
> >>
>
>

Re: Debugging application with modules

[Alex Harui <ah...@adobe.com>]

On 8/5/14 6:02 PM, "mark goldin" <ma...@gmail.com> 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 <ah...@adobe.com> 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" <ma...@gmail.com> 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
>>
>>

Re: Debugging application with modules

[mark goldin <ma...@gmail.com>]

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?


On Tue, Aug 5, 2014 at 5:11 PM, Alex Harui <ah...@adobe.com> 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" <ma...@gmail.com> 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
>
>

Re: Debugging application with modules

[Alex Harui <ah...@adobe.com>]

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" <ma...@gmail.com> 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