OK I finally found the culprit! A colleague asked me to test some DEV setup
on a database change he did. Therefor he told me to install an app which
would edit my localhost file. I did not see this as a related cause until I
saw this possible solution:
https://stackoverflow.com/a/10530208/640907
I tried adding "-nodebug" as an argument for the debug configuration in
Flash Builder but that doesn't help (just as an experiment)
On Tue, Jul 25, 2017 at 12:09 PM, Fréderic Cox
wrote:
> OK this is weird ...
>
> With
>
> FredericBook-2:bin frederic$ ./adl DebugTest-app.xml -nodebug
>
> I get
>
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
wrote:
> F
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
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
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
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 wrote:
> Hi,
>
> I have checked [1] but something does not seem right. It stat
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
las
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
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
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 i
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)/
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 estab
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
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 wrote:
> Thanks for the
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 wrote:
> Same for me.
>
> > On Ju
Same for me.
> On Jul 11, 2017, at 4:18 PM, Jeffry Houser wrote:
>
> To debug a browser based applications, I use Firefox. I couldn't get a
> debugger to work in any other browser.
As a point of clarification, are you trying to debug a desktop AIR
Application or a Browser based application?
You mentioned you downloaded debug players for browsers, but that
you're trying to debug an AIR Desktop application. The two things
should be completely unrelated, so I'm not sur
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" wrote:
18 matches
Mail list logo
