[lwwin]

@bazis wrote:

Hi,

We have tried to reproduce your problem on our side, but could not. Could you please share the exact bashrc file you have and the error you are getting? Does it happen with stand-alone SmarTTY or only with the one embedded in VisualGDB?

Hi, I’ve tried this inside another centos/X86 machine (Linux CentOS-68 2.6.32-358.14.1.el6.i686) and reproduced the error, both steps were :

1. login as root, change /etc/bashrc using vi, simply add “xset -q” at the tail of file, quit with save ( the bashrc should be the same as orig cuz we never changed it before)
2. now logout, and close SmarTTY, and note, check and force close xming
3. then reopen through SmarTTY – Select a Host, DoubleClick the destination PC, and wait… the dialog Authenticating and just simply exit !
4. if at this time, change back the append “xset -q”, SmarTTY is working as usual now!

*. you may try double once more, I found it may take effect at the first time after the machine restart.

Oh, that’s standalone one SmarTTY not integrated inside visualgdb :D, I’ll try that later 🙂

I’ve tried to install latest-VisualGDB trial one, and it seems the same as the standalone one 🙁

[lwwin]

@ket wrote:

Hi,

Based on your logs the ‘info shared’ responses look strange. That could be a reason why the symbols are not available or it could be normal for FlasCC.

Have you tried building and debugging the helloWorld example as described in the official FlasCC documentation at http://www.adobe.com/devnet-docs/flascc/docs/Reference.html#section_gdb ?
Try first gdb command line and then replicate the same in VisualGDB. Is it possible to set breakpoints into your code not only into FlashPlayerDebugger.exe in either case?

Hi,

You mean ‘Try first gdb command line’, is it means using the gdb as “Win> /cygdrive/c/flascc/sdk/usr/bin/gdb.exe hello.swf” as the example inside VisualGDB? If so, I can’t startup without mi flags using custom mode, as shown in the previous log file, or you mean try debug without generate SWF? I would try that, if finding some clues I’ll post new msg later.

And yes, the above logging code is right the hello world code, just one line ‘printf’ code from flascc SDK example 01_helloworld, if I don’t set any breakpoint, it would work right when I startup the program.

The last sentense, I could just set breakpoint at the only one line code of the source code file, and whether it being into FlashPlayerDebugger.exe or not is just my guess and not sure the actually effect.

[lwwin]

@ket wrote:

Hi,

We can look into adding support for FlasCC. Definitely switching the machine interface mode off is not the answer as VisualGDB is a machine.
Could you please post a full GDB log (without mi modifications)? Are there any GDB startup commands that should be entered?

Hi,

thx for the replay, See the attachments Please ;), the .default.log means I just only check ON the save-log flags, without ignoring middle steps ( and I have to abort command or else the VS would block forever ) and, the ignoring one means I also check ON the “ignore *stopped receive after -exec-continue and before ^ running” flag.

and, through many tests, I found that the breakpoint do take effect but break down at FlashPlayerDebugger.exe’s main not at SWF! maybe it is difficult to use machine code debugging according to FlashCC’s Custom GDB implement-method? (btw, it’s open source now named cross-bridge at github https://github.com/adobe-flash/crossbridge) and my friend, who uses flascc to develop, that tell me including eclipse won’t support debugging it even just starting it up (no response), anyway, VisualGDB is the better than that 🙂

[Author]

Posts