Forum Replies Created
-
Posts
-
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.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.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.
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.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.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?
Hi,
Please run the “info sources” command as described here.
The command will list all source files known by GDB and will probably answer why r:/Projects/VA128//jni/arch_android.cpp is not accepted.
Feel free to post the “info sources” output here.Unfortunately, IAR compiler generates debugging data in a format that is incompatible with GDB. Thus, VisualGDB cannot debug it.
However, we could help you switch your project to the GCC toolchain. The toolchain is stable, widely used by community and we can answer your questions on GCC-specific syntax.Thanks for the feedback. Currently it is not supported, however we have added it to v2.8 feature list.
Hi,
Normally it is supported. However, it might not work if your GDB does not report any locals. Please create and send us a GDB log file so that we can tell you how to fix the locals in your case.
Yes, this is supported since v2.4. If you are encountering problems with your version of the STL library, please provide us a screenshot of the expanded watch window so that we can diagnose your problem further.
