Forum Replies Created
-
AuthorPosts
-
supportKeymaster
Hi,
This looks like a hardware bug or the STM32 driver bug. Have you tried contacting the ST support regarding it?
supportKeymasterHi,
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. supportKeymasterHi,
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.supportKeymasterHi,
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?
August 21, 2014 at 02:07 in reply to: Evaluating VisualGDB: some issues, thoughts and questions #3114supportKeymasterHi,
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.
supportKeymasterHi,
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?
supportKeymasterHi,
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.
supportKeymasterHi,
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.supportKeymasterHi,
If you want to attach to an app, please use the ‘Debug Custom APK’ command and select ‘attach to an existing instance’ when prompted.
supportKeymasterHi,
Can you attach a screenshot showing the missing menu item?
supportKeymasterHi,
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?
supportKeymasterHi,
Are you trying to attach to a native tool or an Android App?
August 18, 2014 at 19:59 in reply to: NDK: Eclipse + VisualGDB co-debugging – GDB command timeout #3141supportKeymasterHi,
Please try setting the Android->Debug Options->Do not Query Source Files option. This will disable certain workarounds that depend on the file-list-exec-source-files command, but should overall improve the performance.
supportKeymasterHi,
We received a lot of feedback from different customers regarding poor performance when using Raspberry Pi with WiFi, so we would suspect it to be the main cause. Let us know if you experience any problems with the wired connection.
supportKeymasterHi,
Sorry, please check debug.mak, not flags.mak.
-
AuthorPosts