Forum Replies Created
-
Posts
-
Hi,
The easiest thing to start with would be adding the msys binary directory to PATH when building your makefile (this can be changed on the Build Settings page in VisualGDB Project Properties). That may still require some additional tweaking, e.g. if your Makefile expects the output of ‘pwd’ to have a /cygdrive syntax.
Hi,
You cannot disable the auto-updating of LDFLAGS in stm32.mak, but you can override them directly in Makefile after the “include $(ADDITIONAL_MAKE_FILES)” line.
Hi,
When setting up a new connection you can uncheck the “setup public key” checkbox.
If that does not help, try reflashing your SD card with a clean image. It looks like a strange Raspberry Pi configuration bug.Hi,
This might be an indication that your Raspberry Pi board is doing some heavy math on the public keys. Does the password-based authentication also take lots of time? Does the output of ‘dmesg’ contain anything suspicious about regenerating keys?
Hi,
Sorry, looks like there is a bit of confusion here. Essentially there are 2 totally independent debugging methods:
1. Using the VMWare stub. In this case VMware serves as a back-end for GDB and the Linux kernel does not even know it’s being debugged. This mode is preferred, as the debugging logic is 100% separated from the kernel and it does not involve a slow simulated COM port.
2. Using KGDB via a virtual COM port. In this case VMWare does not know anything about debugging, but the kernel itself runs a debug stub (KGDB) that communicates to GDB via a COM port.We would recommend setting up the first mode, hence please try checking if you can connect to port 8864 or 8865 on the machine where you run your VM (i.e. where vmware-vmx.exe is executing). Your vmware.log file in your VM directory should contain something like this:
2014-06-28T11:25:56.622-07:00| vmx| W110: Debug stub: VMware Workstation is listening for debug connection on port 8864. 2014-06-28T11:25:56.622-07:00| vmx| W110: Debug stub: target remote localhost:8864Please let us know if that works.
Please note that the COM port settings (e.g. speed) are not relevant in this case, as the debugging mechanisms of the Linux kernel are not being used.Hi,
Your VMX file looks like it contains the “stub” setting, so VMWare should be listening on port 8864 or 8865. Are you able to connect to it manually via gdb (target remote localhost:8864)?
Your GDB log also does not contain the ‘target’ command, so it looks like something breaks before that. Are there any error messages you’re getting?Hi,
We’ve just added support for debugging over network to VisualKernel 1.1. Have a look at the following tutorial: http://visualkernel.com/tutorials/network/
Hi,
What VS version are you using? Are you building a MinGW or a Linux project? Does the Errors window contain any IntelliSense-specific errors?
Hi,
That should not normally happen. Typically the connection with Raspberry Pi takes less than 10 seconds.
Please try the following to diagnose it:
1. See if your Raspberry Pi CPU is busy doing something else by running the top command.
2. Try addressing it by IP instead of hostname. Does that change anything?
3. Try using Wireshark to see what happens on the network. Is all the time consumed waiting for one packet or are there several packets exchanged in between? Does with the SSH packets, or are there some suspicious ICMP packets in between?Hi,
Sorry, have not received your settings screenshot yet. BTW, we have released VisualKernel 1.1 that supports debugging kernel over network. Let us know if that works for you better.
Yes, this is correct. You need to specify the library name without the extension and the ‘lib’ prefix. E.g. just ‘pthread’ for libpthread.a. This comes from the syntax of gcc’s -l command that searches for the libraries automatically using the short library names. And as the linking happens on the Windows machine, the libraries should be present there (i.e. copied during sysroot synchronization).
Hi,
The problem happens when VisualGDB runs a temporary script that is supposed to return the Pseudo-TTY name and instead gets something that does not look like a device path. This happens because your SSHD server tries to run some commands just before executing our script. I.e. some of the initialization scripts contain a reference to /usr/bin/X11/xauth, but the file is missing due to some reason.
Note that when you connect with PuTTY, it uses the SSH shell mode, not the SSH command mode, that uses slightly different initialization scripts. Please try looking up what file could be referring to xauth and why it is missing.Hi,
We don’t invest into supporting Atmel devices because they have their own Visual Studio-based IDE (Atmel Studio). If there are third-party tools supporting DragonLink with GDB (i.e. implementing gdbserver), you could easily plug them in. Let us know if you need more details.
You can always upgrade VisualGDB to a higher edition. However, the upgrade price depends on the time of upgrade. E.g. if you upgrade within the first month it’s just the price difference and if you want upgrade after the support/update year ends, you would need to pay the full price again.
