Forum Replies Created
-
AuthorPosts
-
supportKeymaster
Hi,
Running all commands in the interactive shell mode won’t be possible as VisualGDB will not be able to reliably detect when the command exits, however the upcoming VisualGDB 4.3 will check for differences between interactive and command mode variables and allow compensating the differences will running commands.
supportKeymasterOK, than looks like either VisualGDB misses the “*running” notification send by gdb, or gdb itself misses some signal from the app.
Does it work normally when you run “gdb –interpreter mi” via SSH console and run the exact commands VisualGDB issues? Does the “*running” notification appear in GDB output?supportKeymasterHi,
Based on your log it looks like the application you’re debugging with gdb fails to initialize. That usually happens when the application cannot locate the libraries it depends on due to missing directories in LD_LIBRARY_PATH. This can happen because VisualGDB starts gdb using a special ‘command’ mode of SSH that can bypass some startup commands (like motd) depending on your sshd configuration. Please try explicitly specifying the full LD_LIBRARY_PATH to GDB command environment in VisualGDB settings.
If this does not help, we need to understand the virtualization scheme used by docker in order to help you pinpoint the problem. As we have not used docker ourselves, we would need some clarification from you. Does it run a separate virtual kernel, a set of processes under the same kernel, or some layer on top of a single process?
supportKeymasterHi,
If you are interested in upgrading to the Custom edition, please contact sales@sysprogs.com
supportKeymasterHi,
There should not be anything performance-critical between those lines. How large is the RAM on that machine and how much of it is used according to Task Manager?
supportKeymasterHi,
There is no special mode to synchronize only the files included in the project, however you can include and exclude different file masks via the “Files to transfer” field.
If you want to transfer additional directories, simply add a directory transfer action to the pre-build actions on the Custom Build Steps page of VisualGDB Project Properties.supportKeymasterHi,
You can try this one: http://visualgdb.com/tmp/VisualGDB-4.3.1.143.msi
supportKeymasterHi,
Please try enabling the verbose logging (Tools->Options->VisualGDB) and rebuild your project. Does the delay happen after any particular line in the verbose log?
supportKeymasterHi,
This a limitation of the MSBuild system. If you are using Visual Studio 2010+, you can copy the “C:Program Files (x86)MSBuildMicrosoft.Cppv4.0PlatformsWin32” folder under some other name, update the properties files for the new name and manually switch the VisualGDB configurations to that platform. Otherwise, VisualGDB defines additional configurations to existing platforms. A VisualGDB configuration is simply a NMake configuration invoking the VisualGDB build tool and a matching -.vgdbsettings file that stores VisualGDB-specific settings. You can arrange your configurations arbitrarily, as long as those 2 constraints hold.
supportKeymasterHi,
Not with the stable VisualGDB 4.2 release. We have added experimental support for attaching to service processes to the upcoming VisualGDB 4.3 (when your app is already running and has some out-of-process services, VisualGDB will allow attaching to one of them). Would you like to try it out on a preview build?
supportKeymasterHi,
The root cause for this message is incompatibility between the debug information issued by GCC and read by GDB. If you encounter it again, try experimenting with the -gdwarf-
GCC flag. supportKeymasterHi,
Is gcc 4.7 officially included in the latest stable Raspbian distro? If not, it may end up being incompatible with the image.
supportKeymasterHi,
If we make it a background operation and you try to build/edit something while the update is in progress, this may cause unpredictable results. We actually use a cloud-based CDN to cache the BSP/EDP updates, so normally they should be downloaded fairly fast. Does it take more time than a minute or so on your machine? Is it about the toolchain update, BSP update or either of them?
supportKeymasterHi,
The message actually comes from Visual Studio, not VisualGDB. Please try installing the latest service pack.
supportKeymasterHi,
Does it also happen when you launch VisualGDB build from command line? Does your project have lots of source files? Is Visual Studio window responsive during the delay?
-
AuthorPosts