OK this is weird ... With
FredericBook-2:bin frederic$ ./adl DebugTest-app.xml -nodebug I get please debug me ok button clicked setting breakpoint check So it means with "-nodebug" the traces actually show and debugging works .. On Tue, Jul 25, 2017 at 12:06 PM, Fréderic Cox <coxfrede...@gmail.com> wrote: > FredericBook-2:bin frederic$ ./adl DebugTest-app.xml > > invocation forwarded to primary instance > > FredericBook-2:bin frederic$ > > when I already have the application opened. When I open it for the first > time the application opens but I get no output in my console, not even when > I click the button where traces are set and a breakpoint > > On Tue, Jul 25, 2017 at 11:49 AM, Fréderic Cox <coxfrede...@gmail.com> > wrote: > >> Hi Alex, >> >> I tried running adl from command line but nothing happens, I get no >> output. Probably I'm doing it wrong. >> You mentioned "ads" in your e-mail but I guess this is a typo? I do not >> have ads in my bin folder. >> >> I did manage to run swfdump -abc DebugTest.swf and the output contains >> debugline and debugfile info. >> >> Also interesting .. yesterday I created a mobile project which I run on >> the device and debugging works there! It does not for desktop AIR projects. >> >> What is the difference? >> >> On Wed, Jul 12, 2017 at 5:20 PM, Alex Harui <aha...@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] >>> http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e6 >>> 3e3d11c0bf69084 >>> -7fc9.html >>> <http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7fc9.html> >>> >>> On 7/12/17, 1:34 AM, "Fréderic Cox" <coxfrede...@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-debu >>> g/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 <coxfrede...@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-deb >>> ug/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 <aha...@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" <coxfrede...@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 <harbs.li...@gmail.com> >>> wrote: >>> >>> > >>> >>> >> Same for me. >>> >>> >> >>> >>> >> > On Jul 11, 2017, at 4:18 PM, Jeffry Houser < >>> jef...@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. >>> >>> >> >>> >>> >> >>> >>> >>> >>> >>> >> >>> >>> >> >
