[support]

Please try VisualGDB 3.0 Beta 1. The problem is fixed there.

[support]

Hi,

Thanks for reporting this. Fixed in Beta 2.
http://www.visualgdb.com/download/

[support]

Hi,

Could you please send us your .vcprojx file and the .filters files so that we could reproduce and fix your problem?
There was a bug in v2.7 that could cause this, however it was fixed in v3.0.

[support]

Hi,

Yes, the bug is caused by the ‘ps’ command producing slightly different output from the one on most of the Android devices.
We have fixed this in the upcoming VisualGDB 3.0 release. We are planning to release the beta (also supporting vs-android integration) at the end of this week.

[support]

Hi,

Permission granted. If you need an official document, email sysprogs@sysprogs

[support]

Hi,
Done. Please download VisualGDB 3.0.

[support]

Hi,

You can easily use VisualGDB with the free CodeSourcery Lite toolchain.
Please try this instructions on setting up the toolchain: http://www.lpcware.com/content/project/lightweight-ip-lwip-networking-stack/building-lwip/embedded-artists-lpc1788-board/gn

[support]

OK, thanks, we’ll look into it.

[support]

Hi,

Unfortunately, stepping into the functions from C# to VisualGDB-based C++ is not supported.
However, you can start C# debugging in Visual Studio and then attach to the same process with VisualGDB from another Visual Studio instance.
Although stepping between C# and C++ won’t work, you will be able to debug C# code from one Visual Studio instance and the C++ code from another instance.

[support]

Hi,
We are planning a new release this week. Please contact sales@sysprogs.com and we will extend your trial period to 15 days more.

[support]

OK, you’ve convinced me that the current behavior is confusing enough. We’ll add support for reading the intent tags into the upcoming v2.8 release.

[support]

Hi,

Could you please provide more detailed info on what exactly fails on mono 4.0?

[support]

Hi,

VisualGDB indeed launches the first activity from the XML file. Thus you can control it by editing the XML file directly.
If it’s a major inconvenience and you believe making special GUI for it can save time, let us know so that we schedule this feature for further releases.

[support]

Thank you for the log files!
It looks like there’s a bug in gdb 6.x shipped with the latest NDK that it refuses to take fully-qualified file paths on Windows. On ARM targets this is fixed by using prebuilt GDB 7.x that is provided with VisualGDB.
We have added a workaround to the upcoming VisualGDB 2.8 to use file-name-only syntax as a last resort if GDB refuses to accept all other file name variations.

The only workaround with the current version is to issue the breakpoint commands with file-name-only syntax manually (e.g. -break-insert -f arch_android.cpp:116).
Alternatively you could use an ARM target until we release VisualGDB 2.8.

[support]

That is very strange. Is the library actually loaded at the time you set the breakpoint? Could you please run the “info sources” and “info shared” commands just after you set the breakpoint and post the entire log containing all 3 commands here?

[Author]

Posts