Forum Replies Created
-
Posts
-
Hi,
You can use the objcopy tool to add arbitrary sections to an ELF file at given addresses. A sample use of objcopy to replace a section in the file is shown in our Keil tutorial: http://visualgdb.com/tutorials/arm/keil/
Simply take the ELF file you want to debug and use objcopy to attach the contents of other files (.bin files produced from .elf files) at the addresses where you want them to be. Ensure you set the sections flags correctly (see the flags on the main code section) so that GDB can program your file.
Let us know if that works for you.
Are you getting the same error as mentioned in the original message? If yes, it can be caused by the Windows DNS cache and stopping the “dnscache” service might help.
Hi,
Can you ping your remote machine? If no, please check your IP address/subnet mask/gateway settings.
If yes, the firewall on the remote machine might be blocking the connections to the gdbserver. Please try disabling the firewall on the Linux side.
Hi,
We have added the $(TargetFileNameWithoutExtension) variable to the upcoming release of VisualGDB 5.0. The next beta will include support it.
Are you using the same user account for the remote debugging and for logging on to the console? If not, you may need to configure xauth.
When you select “show on remote computer”, VisualGDB simply sets the DISPLAY variable to “:0” redirecting the X11 output to the default server. Can you reproduce the same problem by running “export DISPLAY=:0 && <command>” manually via SSH?
Hi,
It looks like some sort of an incompatibility problem between your device and your toolchain. Please double-check the following:
- Ensure that your toolchain is compatible with the image version on your Raspberry Pi
- Ensure that you have re-synchronized the sysroot of your toolchain with the device
If nothing helps, please try compiling your program directly on Raspberry Pi and let us know if that works.
Hi,
Yes, you can do that as well if it works for you. However many convenient things like running commands on remote machines or transferring additional files would only work via pre/post-build actions (unless you want to script them via SSH/SCP manually).
Hi,
Please you enable GDB logging as described here and submit the detailed GDB log so that we could investigate it.
We would recommend checking in the .vcxproj files and the .vgdbsettings files to your source control system. When other developers add more source files, the checked in Visual Studio project will be updated and you will automatically receive the changes when you update your checkout.
Hi,
How long does it take to program your binary using the official STM32 ST-Link tool? If that tool takes the same time, it’s probably a limitation of ST-Link.
If you want better performance, we would recommend trying out Segger J-Link. It’s more expensive, but it comes with its own GDB stub that is generally better than OpenOCD.
Hi,
Yes, you can customize this via the Debug Settings page of VisualGDB Project Properties (look at the bottom of the page).
Hi,
Unfortunately, Visual Studio variables are not supported. Only VisualGDB variables and your Windows environment variables will work. Can you give an example of you what do you mean by “target name”?
Hi,
Thanks for sharing the solution that worked for you. You can also avoid logging on as root by fixing the permissions in /usr/lib (sudo chmod -R a+r /lib) and specifying “Run GDB as root” in VisualGDB Project Properties.
Well, not exactly years 🙂
Anyway, the final WinCDEmu 4.0 is out. We have also published the source code with all dependencies on GitHub: https://github.com/sysprogs/WinCDEmu
Now that the source code can be conveniently accessed via GitHub, I would like to invite everyone to contribute to the project. I started WinCDEmu many years ago as a hobby project and during these years it has grown to be a nice and nifty tool. However, realistically speaking, I won’t have the capacity in the near future to add any major features to it. That’s why I did my best to make it as easy as possible for everyone to build WinCDEmu and contribute new code to it. The GitHub repository contains one easy-to-build solution that can be opened with VS2010-2015 and it will automatically check for missing dependencies and display instructions on getting/installing them. I will be happy to answer your questions about BazisLib/WinCDEmu structure and to suggest ways of adding the features wanted by the community. I am also open to contributions as long as they don’t break the existing functionality 🙂
Hi,
You can disable the VisualGDB GDB warning window by increasing the GDB command time-out in Tools->Options->VisualGDB->General->Tweaking->GDB command timeout.
If you want to try speeding up the debugging experience, please share a GDB log with timings as described here. It should provide enough information on which exact commands are being slow.P.S. Are you using a USB virtualization software or is ST-Link connected directly to your Windows machine?
