Forum Replies Created
-
Posts
-
Hi,
According to the log you posted, GDB can find the symbols for Application::WidthMonitor::CApplication_WidthMonitor class and cannot find symbols for Lib::ImgProc::CLightBar::DetectEdgesFast(Camera::TImageInfo*).
Please check whether the Lib::ImgProc::CLightBar::DetectEdgesFast(Camera::TImageInfo*) function (can be also mentioned as _ZN3Lib7ImgProc9CLightBar11DetectEdgesEPN6Camera10TImageInfoE) contains the source code in the disassembly file. If no, please run objdump on the .o file corresponding to the cpp file containing the Lib::ImgProc::CLightBar::DetectEdgesFast(Camera::TImageInfo*) function and see whether the source is displayed when dumping the .o file.Please note that when running the “info line” command you should put the function name, not the function calling statement, e.g.:
info line Lib::ImgProc::CLightBar::DetectEdgesFastThe “info line” command will display the source line number that corresponds to a given function and can be used to determine whether the source line information is available for the given module.
Hi,
Thanks for pointing this out. We will add an update to our next release. Please let us know whether you need a hotfix before the release.
Please run the following commands on your Raspberry PI box and provide us with the output:
1. ldd
2. ldconfig -vPlease let us know whether running ldconfig fixes the issue.
BTW, we have improved our STM32 support in VisualGDB 4.0. A tutorial is available here: http://visualgdb.com/tutorials/arm/stm32
Can you please create a new project with the default debug method (e.g. GDB simulator) and send us the created files? This will help us analyze your problem and suggest a solution.
Additionally could you please check your firewall settings? Visual Studio process needs to have internet access in order to download additional packages. If this is not possible, we can provide you with instructions on manually downloading and installing those packages.
Hi,
Which toolchain are you using? Please use our arm-eabi toolchain (it is installed automatically when selected on the toolchain page). Please also note that OpenOCD/J-Link is available starting from VisualGDB 4.0 and won’t work on 3.x.
How often does this happen? We have encountered similar behavior on some versions of MacOS and it looked like a bug in their end of SSH. Could you build newer GDB from sources in your home directory and let VisualGDB use it explicitly?
Hi,
Thanks for your explanations. We have fixed it in Beta 3. We have also added an option (Tools->Options->VisualGDB->General) to override the default file masks used when creating projects.
Hi,
Thanks for reporting this. Could you please let us know how what exactly you are doing to browse the folder? Please feel free to attach a screenshot or a step-by-step description.
Hi,
First starting the app and then attaching to it is the default behavior of the Android debugger.
You can override it by selecting Android->Debug Options->Debug App Startup in Visual Studio.
Once you select that option, starting debugging will take slightly longer, but all your initialization breakpoints will be hit.Hi,
Thanks for reporting this. Please feel free to report further bugs on this forum or simply send emails to support.
There was indeed a bug on our side. The build/debug customization pages were intended to appear in Custom and Ultimate editions only and activating them in other editions crashed the dialog as the underlying logic was not present.
We have updated the installer.Hi,
Thanks for reporting this. We could not reproduce it on our side. Could you please send us your .vgdbsettings file so that we can diagnose this further?
Hi,
Thanks for reporting this. The project settings from the previous versions of VisualGDB are saved to the -.old file. Simply change the extension back to .vgdbsettings to restore it.
