[ket]

Hi,

VisualGDB uses Apache Ant to build the Java part of Android apps. That means you should follow the steps of adding Java libraries to Ant projects. Alternatively you can also import the Android manifest to eclipse and use the ADT plugin to add the library, the project files used by ADT and Ant are the same and any change made in eclipse will be used by Ant during building as well. Normally referenced jar files are simply copied into the libs folder.

[ket]

Hi,

VisualGDB version 4.2. enabled the start without debugging feature of Visual Studio. You can use the Debug->Start Without Debugging option to start the program without a debug session, this option will take care of both deploying and starting the program.
If you wish to upload the built program automatically after each build then you can add a custom post-build step to do so.

[ket]

Hi,

Thank you for feature request. We have added it to our list of features under consideration.

[ket]

Hi,

Please use the wiringPi tutorial as a reference on how to use libraries with cross-toolchains such as the Raspberry Pi toolchain:
http://visualgdb.com/tutorials/raspberry/wiringPi/

The error is likely shown as the include directory has not been added to the settings, to fix this error add the include directory of the library to the include directories on the Makefile settings page in VisualGDB. Adding the include directory there will also add it to IntelliSense directories.

[ket]

Hi,

This problem has been reported before and a warning message was added in VisualGDB version 4.2.

[ket]

Hi,

Is there a gdb included with the toolchain at all just with a different name or location? If yes, then you can rename and/or move the gdb to the location VisualGDB expects it. If there is no gdb provided, then a project using this toolchain cannot be debugged. You could try to create a dummy gdb to fulfill VisualGDB Linux project expectations or simply make a Custom project that you use for building only.

Another option would be to use the Windows arm-eabi cross-toolchain (http://gnutoolchains.com/arm-eabi/) that we provide instead if that would also fit your project needs. That toolchain should be suitable if you are targeting a bare metal embedded system. If you are targeting an ARM device with an operating system, then for example the Raspberry Pi cross-toolchain would suit more.

[ket]

Hi,

Thank you for the reproduction steps, we will try to reproduce and fix the issue.

vgdbsettings files essentially are the project files, they contain the necessary information for building and debugging. They are meant to extend the Visual Studio project files. What is your use case to need a global vgdbsettings file?

[ket]

Hi,

Currently VisualGDB and SmarTTY do not support IPV6. The upcoming versions however will.
The problem occurs because sometimes the Windows network connection chooses to use IPV4 and sometimes IPV6, whenever it chooses to use IPV6 then you will get the error. You can try disabling the usage of IPV6 from Network Connections under Windows.

[ket]

Hi,

It could be a gdb issue, which version are you using? Have you tried updating both gcc/gdb to see if that solves the issue?

Please give us a gdb log for further analysis. You can enable diagnostic gdb logging on the GDB settings page of VisualGDB Project Properties. Then start debugging, replicate the issue, stop debugging and give us the log from your project directory.

[ket]

Hi,

VisualGDB will try to take the target name from the dependent project’s makefile. Having all the project files in the same directory could trigger some bug in VisualGDB.

Please go to Tools->Options->VisualGDB and enable verbose output. Then rebuild the solution, the build log in the Output window should show the detected dependent projects and their makefiles. Please give us this log along with the full paths of both projects’ makefiles and project files (.vcproj or .vcxproj files).

[ket]

Hi,

We usually hear what devices VisualGDB users are using if there any issues. As we have not heard of any users using the Amazon Fire TV box, that could mean two things. Unfortunately, there is no way of knowing until you try it out yourself with a newer version of VisualGDB.

If you switch to a trial, you will be able to still switch back to the old version of VisualGDB you were using before. Since VisualGDB 4.x has a newer project settings format, a back-up copy of your older settings will be made before converting. Also if there is an issue that we can fix within VisualGDB, then we would also likely have a fix out before your trial expires.

[ket]

Hi,

Much has changed about VisualGDB since version 2.7, including the global verbose option and the launcher log that we would really need to see in this case. It could also be that you are experiencing an issue in VisualGDB that was fixed in newer versions. Also, any change to VisualGDB we would make would be released in a 4.1r release or in the upcoming 4.2 version of VisualGDB.

Please contact our sales team for a license renewal quote or trial extension code, so you could try the latest VisualGDB version before renewing. You could also try to see if using the newest version released during your one year support period works, but if there are issues, then any change would be released in the new version of VisualGDB and that issue should be replicable with the latest release of VisualGDB.

[ket]

Hi,

This looks like a Visual Studio issue. Have you tried waiting until the IntelliSense information is updated? Maybe this will help the message not repeat, as usually the IntelliSense information is generated only once when the project without the cached IntelliSense information is opened. This can take several minutes for a large project. Any subsequent usage of the same project should not have this message come up as any IntelliSense updates should be small and done in the background.

You can try disabling IntelliSense, but there may be no good way to turn IntelliSense completely off. It is possible to turn certain features off, but this may not affect IntelliSense information caching that your issue seems to be about. Disabling IntelliSense will not affect building or debugging your projects, however text editor features such as code suggestion will not be available.

[ket]

Hi,

Strange that the VisualGDB options do not appear, which version of VisualGDB are you using? However, the verbose option from the options does not make the log appear, it just adds a bit more detail. Do you have a VisualGDB Launcher Output log available from the Output window?

Java debugging and native debugging work differently, based on the current error it is too early to tell whether native debugging will work. The current error is probably something we can adjust to in VisualGDB, but we need to know at which stage of launching it happens.

[ket]

Hi,

If the device shows up for ADB, then it should be possible to debug the device. However more exotic Android-based devices can have issues with their images that can accidentally or deliberately break the debugging possibility.

Based on this error message, it is thrown by VisualGDB itself due to something unexpected during launch. The ADB log looks fine and does not contain anything unusual. Please go to Tools->Options->VisualGDB and enable verbose output from there. Then please look in the Output window and change the filter there to show output from VisualGDB Launcher Output, then give us this log.
Also, are you trying to debug com.gabysoft.flippixaaa or some other app? Does just deploying or launching the app (Android menu commands) without debugging work?

[Author]

Posts