[support]

Hi,

If you are using a cross-toolchain (that implies using gdbserver), your program’s output will be displayed in the gdbserver window. VisualGDB includes a terminal emulator, so if your program is using the common ANSI escape sequences, VisualGDB will be able to handle them properly.

If it looks like the terminal emulation is not working, please let us know the details and we will look into this.

[support]

Hi,

Thanks for the update. The toolchain shipped with VisualGDB indeed uses a slightly different naming scheme, however should be able to locate the correct libraries as long as you specify the ARM core and the floating point mode. Either way, if switching to the original ARM toolchain solves the problem, VisualGDB fully supports it, so we would recommend simply keeping that toolchain.

[support]

Hi,

Good to know it works. If you encounter further problems, feel free to let us know and we will help.

[support]

Hi,

You can use the Call Stack window to see the code that triggered the hard fault (unless the stack got corrupt or the stack pointer is set incorrectly). In the latter case please try simply putting a breakpoint in Reset_Handler and stepping through the initialization code to discover the line triggering the hard fault.

[support]

Hi,

This could have been caused by the updated toolchain engine that does automatically finds the toolchain during build instead of hardcoding its location in the project properties. Some manual modifications to the project files that previously worked with v5.1 and v5.2 would not work with v5.3 due to this update.

Either way, feel free to let us know more the details of the error you get and we can help you get v5.3 to work.

[support]

Hi,

If you are using MSBuild, the map file should already be created in the same directory as the ELF file. You can also override it via the Linker Settings -> Advanced (e.g. to $(OutDir)file.map).

Based on our quick research, the -save-temps option always saves the temporary files in the current directory (VisualGDB sets this to the project directory so that relative paths specified in project properties would work as expected). The only way we could suggest to override it would be to add a custom post-build step that would move the generated files to $(OutDir).

Regarding the ELF files, we would advise diagnosing it as follows:

• Dump build command lines from both Eclipse and VisualGDB. E.g. using procmon. If you are using MSBuild, VisualGDB stores all command lines in the .rsp files, so you can simply reuse them.
• Build the project manually using both command line sets. Ensure that the ELF files still produce different results.
• Try linking the files compiled using the Eclipse command lines using the VisualGDB linker command line. This should tell if the problem is related to the linker or the compiler.
• If the problem is linker-related, compare the link command lines and try removing half of the differences to see if this fixes the problem. Repeating this a few times should help pinpoint the setting responsible for the error.
• If the problem is compiler-related, use a similar approach to pinpoint the source file causing the problem and then the command line argument causing it.

Unfortunately this does involve non-trivial amount of troubleshooting, however given the size/complexity of the project, it could be easier than trying to guess the offending setting otherwise.

[support]

Hi,

Sorry for the delay. It looks like 2 known issues:

1. You appear to be using lwIP in a mode where it tries to redefine the timeval structure that is already defined in the gcc toolchain. Double-clicking on the error message should open the related definition:

#ifndef LWIP_TIMEVAL_PRIVATE
#define LWIP_TIMEVAL_PRIVATE 1
#endif

#if LWIP_TIMEVAL_PRIVATE
struct timeval {
  long    tv_sec;         /* seconds */
  long    tv_usec;        /* and microseconds */
};
#endif /* LWIP_TIMEVAL_PRIVATE */

Simply defining LWIP_TIMEVAL_PRIVATE to 0 via Preprocessor Macros should resolve this (VisualGDB does it automatically when referencing lwIP via VisualGDB Embedded Frameworks, but cannot guess it if you are importing a 3rd-party project).

The problem with syscalls.c looks similar – please examine the file and modify it to avoid redefining the timezone struct.

2. You are building a source file meant for hardware floating point mode using a software FP setting. Please change the FP setting to hard via the first page of VisualGDB Project Properties.

[support]

Hi,

This looks like a configuration problem on your Raspberry Pi. Please try using a clean SD card image and installing Qt on top of it, or follow these instructions on repairing libEGL permissions.

[support]

Hi,

Looks like the underlying build process produced some errors that are not recognized by Visual Studio. Please use the View->Output window to see the entire build output and check it for error messages explaining what is going on.

[support]

Hi,

It looks like your support period has expired. To keep on receiving technical support please renew your support here: https://sysprogs.com/splm/mykey

[support]

Hi,

Yes, sorry it got delayed due to changes in kernel debugging of Raspberry Pi 3 vs. Raspberry Pi 2 . We have a relatively stable pre-release build available here: http://sysprogs.com/files/tmp/VisualKernel-3.0.1.2043.msi

We are still figuring out the last details and are expecting to release a beta this week.

[support]

Hi,

Thanks for the example. We have just tried reproducing this on a clean VS (with a native C++ project),  but unfortunately could not get the same behavior. Perhaps the behavior you are describing is caused by a 3rd-party add-in (e.g. Visual Assist?).

Either way, we could add an option for choosing what gets selected when you type “something->” or “something.”, although this would get a relatively low priority and will be included only in one of the late builds of v5.4.

[support]

Hi,

If closing all windows doesn’t help, please also ensure you don’t have the “show threads in source” option enabled. It would also result in Visual Studio querying all VisualGDB threads.

If you are not sure how to interpret the log file to find the critical paths from the timing perspective, please feel free to attach the log here (or send it to our support email) and we can check it for common problems.

The error message you mentioned looks like a gdb/gdbserver bug. Trying a different version of gdb might solve this.

[support]

Hi,

Sorry, this won’t work as VisualGDB would still try to specify “-G Makefile” internally. As a workaround, please modify the .vgdbsettings (or .vgdbcmake) file as shown below:

<Build xsi:type="com.visualgdb.build.cmake">
    <!-- ... -->
    <CMakeMakefileType>Ninja</CMakeMakefileType>
</Build>

We do agree that this workaround is inconvenient and will include a GUI setting for this in the next major update.

[support]

Hi,

Sorry, this is not yet supported, although is planned for the upcoming VisualGDB 5.4.

[Author]

Posts