Forum Replies Created
-
Posts
-
Hi,
The rebuild error is a known issue and can be safely ignored. Simply build the project afterwards and it will build properly.
The TICK_INT_PRIORITY issue can be solved by regenerating the Device-Specific files folder (change the MCU type and restore it back in VisualGDB Project Properties).Thanks for the kind words. Making a product that is powerful and easy to use at the same time is our main intent.
If you like VisualGDB, you can help it find new users by spreading the word. And if you have suggestions on improving it further, do not hesitate to post them here.Hi,
This looks like a hardware bug or the STM32 driver bug. Have you tried contacting the ST support regarding it?
Hi,
Chroot can be a problem here. Public key authentication setup requires access to
/.ssh and if it becomes unavailable as a result of the chroot call, VisualGDB cannot physically do the setup.
You can do the setup manually by running VisualGDB.exe /dumpsshkey:file.txt and then appending the contents of file.txt to/.ssh/authorized_keys on the remote machine. Hi,
Sorry for the delayed reply. We have made a detailed tutorial on targeting unsupported devices here: http://visualgdb.com/tutorials/arm/legacy/
Let me know if you have any questions.Hi,
We’ve released an updated toolchain based on gcc 4.9.1 that resolves some issues and includes a newer newlib. Does your problem still happen with that version?
Hi,
Sorry for the delayed reply. We are currently investigating a potential regression with our updated ARM toolchain. We will address your issues within the next week. Sorry again for the delay.
Hi,
The previous version did not include the initialise_monitor_handles() method at all. In the current version it is used by the weak implementations of syscalls that can be overridden. Are you calling it initialise_monitor_handles() explicitly, or is it called by some syscall you are invoking?
Hi,
Based on our statistics the Kinetis devices are among the least commonly used. Hence we will be prioritizing support for other device families before. If you want to get it to work earlier, we can provide instructions on specifying the necessary flags manually. Just let us know.
Hi,
Yes, you can override the SSH port by specifying host:port in the “host name” field.
During “configuring” stage VisualGDB adds your public key to ~/.ssh/authorized_keys. If it hangs in this stage, please check whether the file is writable.
You can also disable the “setup public key authentication” and use the password instead.Hi,
If you want to attach to an app, please use the ‘Debug Custom APK’ command and select ‘attach to an existing instance’ when prompted.
Hi,
This looks like a GDB bug (https://code.google.com/p/android/issues/detail?id=67938). Can you try experimenting with other toolchain versions in the NDK and/or different Android platform versions?
