Forum Replies Created
-
Posts
-
Hi,
When we tested it on our side the problem never happened because the Debug directory was created by qmake, so the ‘mkdir’ command was never executed.
Have you changed any files that could result in a change of this behavior? Does doing a full rebuild solve the problem?Hi,
This is the limitation of the manual shared folder mode. You can overcome it by switching to the “shared windows folder mode”.
Simply select “Use a shared Windows folder” in the Project Properties, click “Provide information required to mount the local folder” and select your shared Windows folder and the Linux mount point.
This will provide enough information for VisualGDB to know which directories are part of the shared folder and which are not and thus need to be downloaded.E.g. if you mapped e:projects to /mnt/projects, VisualGDB will open files in /mnt/projects/my_project as well as in /mnt/projects/some_other_project directly, as it will know that all files under /mnt/projects are a part of the Windows share.
Hi,
This can be an indication of missing tools or a problem in your QT configuration. If you click ‘ignore’ is the project created? Do you encounter any problems while building or debugging it?
Just FYI: we have patched our STM32 linker scripts to include this fix. You can re-download the STM32 package from the Wizard to get the new fixed scripts.
Hi,
We have looked into it and added a workaround to VisualGDB 4.1r7. Please note that you can also resolve this issue by updating your GDB to 7.6.
We have sent you the source code for the STLTypeVisualizers. If you encounter any issues with it, please let us know.
Regarding octal display, GDB sometimes uses it internally, but we usually convert the values to either decimal or hexadecimal form. If you encounter octal output in some cases, please provide us with repro steps so that we could investigate and fix it.The compilation and IntelliSense use two independent source parsing mechanisms, so it could happen that IntelliSense shows false positive errors when its mechanism runs out of sync with the build mechanism.
Regarding svc_uif.h file, is C:UsersUporabnikAppDataLocalVisualGDBRemoteSourceCache192.168.3.207 005include referenced in Include Search Path (Visual Studio Project Properties -> NMake -> Include Search Path)?If __STDC__ is not present in the .h file, this can be happening because GCC does not report it when being tested with your configuration settings. This can be specific to your GCC version or some settings. The easiest workaround would be to create a new file (e.g. called gccfix.h), add it to ‘forced includes’ in Visual Studio Project Properties -> NMake and add the following code to it:
#ifdef _MSC_VER #define __STDC__ #endifThis should provide IntelliSense with the missing definitions. _MSC_VER is a macro that is defined by Microsoft Compiler (and Microsoft IntelliSense engine) and won’t be present during build with GCC.
This is strange. __STDC__ should be defined in a gcc_Debug.h file in your project directory and this file should be added to ‘forced includes’ in Visual Studio project properties. Could you please recheck whether the file contains the __STDC__ and whether it’s parsed by IntelliSense?
The structure of the STL containers can be different in your toolchain. Please go to the GDB Session pane, select “Raw GDB Output”, add your vector to the Watch window, expand it and send us the contents of the GDB Session window. It will contain GDB commands issued by VisualGDB that should explain why STL vector visualization is not working.
Please try surrounding the library list with -Wl,–start-group and -Wl,–end-group. Note that our latest Raspberry toolchain contains the fix that eliminates the need to specify full path for libraries. You can now simply mention them in the LIBRARY_NAMES; dependent libraries will be included automatically. To use this feature you will need to download the latest version of the Raspberry toolchain.
Hi,
We have tried to reproduce your problem on our side, but could not. Could you please share the exact bashrc file you have and the error you are getting? Does it happen with stand-alone SmarTTY or only with the one embedded in VisualGDB?
Hi,
Yes, you can make a workaround. First of all, if you are flashing your program using the bootloader (or any other way that ensures correct FLASH layout), you can simply disable “program FLASH memory” checkbox in VisualGDB Project Properties and VisualGDB won’t touch the contents of your FLASH memory.
Alternatively you can get your bootloader code included into the resulting ELF file during build. This can be accomplished by declaring an array containing your bootloader code, placing it into a separate section and modifying the linker script to put this section at the beginning of the FLASH. I.e. you will first need to generate a file like this from your bootloader image (.bin file, not the .elf file):
__attribute__((section(".bootloader"))) char test[] = {0x01, 0x02, ...};Then you need to change the linker script to put the .bootloader section before anything else:
SECTIONS { .bootloader : { . = ALIGN(4); KEEP(*(.bootloader)) FILL(0xff) . = 65K; } > FLASH
...
}Please double-check everything by reading the .map file (or looking at the generated .bin file).
P.S. The FLASH Security bits mentioned in the previous post are used by Freescale Kinetis devices, so you don’t need to worry about them if you are using STM32.
Yes, it is possible to configure VisualGDB to place your code starting at a different address. Please see this thread for an example: viewtopic.php?f=5&t=2777
Note that if you are using Freescale Kinetis, the FLASH region at addresses 0x400-0x410 should contain FLASH security bits. If you change your linker script, ensure that the security bits end up in the same place.
Please also note that if you program your project starting at 64KB using VisualGDB, it will fill the first 64KB with zeroes and not just keep them unchanged.
