You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flex.apache.org by Fréderic Cox <co...@gmail.com> on 2017/07/11 11:43:29 UTC

Flash Builder desktop debugging issue

Hi,

I have a problem since a few days that is driving me absolutely nuts.
Flash Builder 4.7 is unable to connect to the debugger. It works for web
projects but not for AIR desktop projects.

I have tried numerous things like cleaning workspace, restarting FB, ..
nothing works.

I have downloaded the debug player for Chrome, Firefox and standalone.

flashbuilder.eu/flash-player-version.html tells me I have the debug player
installed correctly for both.

I have placed the Flash Player debugger in /Applications/Adobe Flash
Builder 4.7/player/mac/26.0/Flash Player.app and used that path in the
debug pane of the Flash Builder preferences so it should use that one ...

Although the name is Flash Player.app and not Flash Player Debugger.app
when I open it it shows as the Flash Player Debugger so that looks to work
also.

Any tips on how to solve this problem?

Thanks

Re: Flash Builder desktop debugging issue

Posted by Josh Tynjala <jo...@gmail.com>.

If you're having trouble with AIR, the Flash Player version installed
shouldn't matter.

Have you double checked your compiler options? You should make sure your
project isn't setting -debug=false somehow. I forgot that I had done that
once!

- Josh


On Jul 11, 2017 4:48 AM, "Fréderic Cox" <co...@gmail.com> wrote:

Hi,

I have a problem since a few days that is driving me absolutely nuts.
Flash Builder 4.7 is unable to connect to the debugger. It works for web
projects but not for AIR desktop projects.

I have tried numerous things like cleaning workspace, restarting FB, ..
nothing works.

I have downloaded the debug player for Chrome, Firefox and standalone.

flashbuilder.eu/flash-player-version.html tells me I have the debug player
installed correctly for both.

I have placed the Flash Player debugger in /Applications/Adobe Flash
Builder 4.7/player/mac/26.0/Flash Player.app and used that path in the
debug pane of the Flash Builder preferences so it should use that one ...

Although the name is Flash Player.app and not Flash Player Debugger.app
when I open it it shows as the Flash Player Debugger so that looks to work
also.

Any tips on how to solve this problem?

Thanks

Re: Flash Builder desktop debugging issue

Posted by Josh Tynjala <jo...@gmail.com>.

Inside the your SDK, the adl executable is used to debug AIR apps. (adl =
AIR debug launcher)

If nothing in your SDK changed, then it's probably related to compiler
arguments or something related to building the SWF.

- Josh

On Tue, Jul 11, 2017 at 8:11 AM, Fréderic Cox <co...@gmail.com> wrote:

> Thanks for the replies.
>
> The problem is related to AIR debugging on desktop. I did not change my
> Apache Flex SDK so I really can't understand what caused the problem.
>
> Which debugger is used for AIR and where is it located?
>
> On Tue, Jul 11, 2017 at 3:41 PM, Harbs <ha...@gmail.com> wrote:
>
> > Same for me.
> >
> > > On Jul 11, 2017, at 4:18 PM, Jeffry Houser <je...@dot-com-it.com>
> > wrote:
> > >
> > > To debug a browser based applications, I use Firefox.  I couldn't get a
> > debugger to work in any other browser.
> >
> >
>

Re: Flash Builder desktop debugging issue

Posted by Alex Harui <ah...@adobe.com.INVALID>.

I'm not sure you "must" have an mm.cfg file.  I think if you don't have
one, you just won't get certain kinds of information in the flashlog.txt
but the debugger would still work.  Mine looks like Josh's so you can try
starting with that.

If you had an mm.cfg file, Flash Builder might have written to it if you
tried to profile an application.  If it started out empty, it would be
modified to point to the profiler plugin, then that line would be removed
when the profiling session ended.

I would say that the next step is to use the command-line debugger (fdb).

-Alex

On 7/14/17, 7:11 AM, "Josh Tynjala" <jo...@gmail.com> wrote:

>I have an mm.cfg in my home directory, but it isn't empty. It contains the
>following two lines, plus an empty line:
>
>ErrorReportingEnable=1
>TraceOutputFileEnable=1
>
>- Josh
>
>On Fri, Jul 14, 2017 at 1:17 AM, Fréderic Cox <co...@gmail.com>
>wrote:
>
>> Hi,
>>
>> I have checked [1] but something does not seem right. It states (for
>>Mac):
>>
>> Flash Player first checks the user’s home directory (~). If none is
>>found,
>> then Flash Player looks in /Library/Application Support/Macromedia
>>
>> So I checked my user directory and there is an mm.cfg file with 0 bytes
>> last modified 3 days ago ..
>>
>> I don't know what I did 3 days ago, maybe update Adobe AIR but I'm
>>unsure.
>> So I deleted this empty file and checked for /Library/Application
>> Support/Macromedia but in there I don't have a mm.cfg file. I do have a
>> mms.cfg file there but it seems to be unrelated.
>>
>> Anybody have any idea why I would have an empty mm.cfg in my home
>>directory
>> and what I should do to fix this?
>>
>> [1]
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fhelp.adob
>>e.com%2Fen_US%2Fflex%2Fusing%2FWS2db454920e96a9e51e63e3d11c0b&data=02%7C0
>>1%7C%7Cf530badb46bf47b5f10b08d4cac254db%7Cfa7b1b5a7b34438794aed2c178decee
>>1%7C0%7C0%7C636356383373875330&sdata=BdpsJXlBvX3ZtvmcFj4w4%2FrcBU1ArigCnv
>>jPg7sBTJI%3D&reserved=0
>> f69084-7fc9.html
>>
>> On Thu, Jul 13, 2017 at 3:51 PM, Fréderic Cox <co...@gmail.com>
>> wrote:
>>
>> > Thanks for the help Alex, I'll check it tomorrow when I am back in
>>office
>> >
>> > On Wed, Jul 12, 2017 at 5:20 PM, Alex Harui <ah...@adobe.com.invalid>
>> > wrote:
>> >
>> >> Location of mm.cfg is listed here [1]
>> >>
>> >> If mm.cfg is ok, next step is to use the command-line debugger.  For
>>AIR
>> >> apps, you have to launch bin/fdb from the SDK folder, then type 'r'
>>and
>> >> return.  This should cause the debugger to wait for the next runtime
>>to
>> >> launch.
>> >>
>> >> Then run the ads command you see in the launch details below.  The
>> >> debugger report that it connected.  Use the 'c' command until the AIR
>> app
>> >> comes up.  If the AIR app just runs and nothing happened in the
>> debugger,
>> >> the next step is to use "bin/swfdump -abc"  on the SWF in bin-debug.
>> Look
>> >> for 'debugline' and 'debugfile' in the output.  If it isn't there,
>>then
>> >> some how the build process is not placing debug information into the
>> SWF.
>> >> Then it is time to check all of your settings.
>> >>
>> >> HTH,
>> >> -Alex
>> >>
>> >> [1]
>> >> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fhelp.adob
>>e.com%2Fen_US%2Fflex%2Fusing%2FWS2db454920e96a9e51e6&data=02%7C01%7C%7Cf5
>>30badb46bf47b5f10b08d4cac254db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0
>>%7C636356383373875330&sdata=JZxxBSz2V%2FL1BhRwv%2Ft31ji1GUW8z7qEozVSP4P%2
>>BIuI%3D&reserved=0
>> >> 3e3d11c0bf69084
>> >> -7fc9.html
>> >> 
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fhelp.ado
>>be.com%2Fen_US%2Fflex%2Fusing%2FWS2db454920e96a9e51e63e3d11c0b&data=02%7C
>>01%7C%7Cf530badb46bf47b5f10b08d4cac254db%7Cfa7b1b5a7b34438794aed2c178dece
>>e1%7C0%7C0%7C636356383373875330&sdata=BdpsJXlBvX3ZtvmcFj4w4%2FrcBU1ArigCn
>>vjPg7sBTJI%3D&reserved=0
>> f69084-7fc9.html>
>> >>
>> >> On 7/12/17, 1:34 AM, "Fréderic Cox" <co...@gmail.com> wrote:
>> >>
>> >> >When I change my SDK it is giving me the same problem.
>> >> >
>> >> >Process terminated without establishing connection to debugger.
>> >> >
>> >> >trace1
>> >> >trace2
>> >> >
>> >> >Launch command details:  "/Applications/Adobe Flash Builder
>> >> 4.7/sdks/4.6.0
>> >> >(AIR 3.8)/bin/adl" -runtime "/Applications/Adobe Flash Builder
>> >> >4.7/sdks/4.6.0 (AIR 3.8)/runtimes/air/mac"
>> >> >/Users/frederic/Desktop/Exuvis/Mediahuis/DebugTest/bin-
>> >> debug/DebugTest-app
>> >> >.xml
>> >> >/Users/frederic/Desktop/Exuvis/Mediahuis/DebugTest/bin-debug
>> >> >
>> >> >So it must be something external, no?
>> >> >
>> >> >On Tue, Jul 11, 2017 at 6:08 PM, Fréderic Cox
>><co...@gmail.com>
>> >> >wrote:
>> >> >
>> >> >> Thanks a lot for your help.
>> >> >>
>> >> >> I have created a new project and the same problem arises so it has
>> >> >>nothing
>> >> >> to do with compiler options. I created a project DebugTest and in
>> >> >> creationComplete I've put two traces and a breakpoint. The
>>debugger
>> >> does
>> >> >> not connect and shows:
>> >> >>
>> >> >> Process terminated without establishing connection to debugger.
>> >> >>
>> >> >> trace1
>> >> >> trace2
>> >> >>
>> >> >> Launch command details:
>> >> >>/Users/frederic/ApacheFlex/sdk/4.15.0_AIR20/bin/adl
>> >> >> -runtime /Users/frederic/ApacheFlex/sdk/4.15.0_AIR20/runtimes/air/
>> mac
>> >> >>
>> >> >>/Users/frederic/Desktop/Exuvis/Mediahuis/DebugTest/bin-
>> >> debug/DebugTest-ap
>> >> >>p.xml
>> >> >> /Users/frederic/Desktop/Exuvis/Mediahuis/DebugTest/bin-debug
>> >> >>
>> >> >> I have disabled all my chrome and firefox extensions but no luck.
>> >> >>Should I
>> >> >> restart my Mac? Going to try that now...
>> >> >>
>> >> >> Where do I find mm.cfg?
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Fréderic
>> >> >>
>> >> >> On Tue, Jul 11, 2017 at 5:38 PM, Alex Harui
>><aharui@adobe.com.invalid
>> >
>> >> >> wrote:
>> >> >>
>> >> >>> Hi Fréderic,
>> >> >>>
>> >> >>> The actual debugger is the same in Flash Builder.  Flash Builder
>> has a
>> >> >>> built-in debugger that tries to connect to a debugger Flash
>>Player
>> in
>> >> >>>the
>> >> >>> browser, or to the Air Debug Launcher (ADL).
>> >> >>>
>> >> >>> When you Run/Debug a Desktop app in Flash Builder, I think it
>>should
>> >> >>> always launch ADL.  I don't think there is any other way to set
>>up
>> the
>> >> >>> launch.  If the app comes up but the debugger doesn't connect,
>>you
>> can
>> >> >>> probably assume ADL is being launched.
>> >> >>>
>> >> >>> If the debugger isn't connecting to ADL, as Jeffry mentioned, if
>>you
>> >> >>>set
>> >> >>> debug=false as a compiler option, the runtime will not try to
>> connect
>> >> >>>to
>> >> >>> the debugger.
>> >> >>>
>> >> >>> Another way the debugger fails to connect is if some other Flash
>>or
>> >> AIR
>> >> >>> application is also launching around the same time as your
>> >> application.
>> >> >>> The debugger isn't looking for your app specifically, it is
>>looking
>> >> for
>> >> >>> the first new instance of a Flash or AIR runtime.  I've seen
>>little
>> >> >>> browser plugins fool the debugger.  I've seen SWFs in the
>>preloader
>> of
>> >> >>>a
>> >> >>> Flex app connect instead of the main app.  I've seen an Flash
>> >> animation
>> >> >>> embedded in the main app connect instead of the main app.
>> >> >>>
>> >> >>> Also, I've seen where the profiler is set up for launch as well.
>> >> Check
>> >> >>> your mm.cfg file to see if the profiler is getting launched.
>> Sometimes
>> >> >>>if
>> >> >>> a profiler session crashed or is aborted, the mm.cfg is not
>> restored.
>> >> >>>
>> >> >>> HTH,
>> >> >>> -Alex
>> >> >>>
>> >> >>> On 7/11/17, 8:11 AM, "Fréderic Cox" <co...@gmail.com>
>>wrote:
>> >> >>>
>> >> >>> >Thanks for the replies.
>> >> >>> >
>> >> >>> >The problem is related to AIR debugging on desktop. I did not
>> change
>> >> >>>my
>> >> >>> >Apache Flex SDK so I really can't understand what caused the
>> problem.
>> >> >>> >
>> >> >>> >Which debugger is used for AIR and where is it located?
>> >> >>> >
>> >> >>> >On Tue, Jul 11, 2017 at 3:41 PM, Harbs <ha...@gmail.com>
>> >> wrote:
>> >> >>> >
>> >> >>> >> Same for me.
>> >> >>> >>
>> >> >>> >> > On Jul 11, 2017, at 4:18 PM, Jeffry Houser <
>> >> jeffry@dot-com-it.com>
>> >> >>> >> wrote:
>> >> >>> >> >
>> >> >>> >> > To debug a browser based applications, I use Firefox.  I
>> couldn't
>> >> >>>get
>> >> >>> >>a
>> >> >>> >> debugger to work in any other browser.
>> >> >>> >>
>> >> >>> >>
>> >> >>>
>> >> >>>
>> >> >>
>> >>
>> >>
>> >
>>