[Lonko]

Dear

Yep that was it… changed the makefile to visualgdbs and it works

Thank you!

BR

[Lonko]

Dear

 

thank you for your response, the demo project is a default visualgdb linux console project that has helloworld inside

i did not take any other project or sources.

 

br

[Lonko]

Dear,

 

we created new project and now it works. This probably happenend as the projects are up to 4 years old at least.

 

p.s. Which setting disables this???

VisualGDB version: 5.5.4.3540
—————— at2 ——————
at2: Deployed item size () does not match the original item size (209632). If this is a false positive, try disabling deployment validation via global VisualGDB Settings. —> System.Exception: Deployed item size () does not match the original item size (209632). If this is a false positive, try disabling deployment validation via global VisualGDB Settings.
at s01.e1(f11 b, List`1 a)
at s01.h1.c(f11 a)
at o72.u`1.g(f11 a)
at VisualGDB.Add_In.Tool_Windows.WPF.DockedProgressPresenter.RunItemizedOperation(Action`1 operation, String caption, ng exceptionHandler, String[] stages)
at o72.y[_ResultType](gh1`1 b, String c, Int32 a, String[] d)
at s01.t1()
— End of inner exception stack trace —
at s01.t1()
at s01.w1(DebugCustomizationSettings a, Boolean b)
at e32.k2()
at wo1.c2()
at VisualGDB.GDBDebugEngine.f1(z71 a, p b)
trace=[s01.t1:200, s01.w1:53, e32.k2:5442, wo1.c2:22, VisualGDB.GDBDebugEngine.f1:58]
—————— Inner exception ——————
—————— System.Exception ——————
System.Exception: Deployed item size () does not match the original item size (209632). If this is a false positive, try disabling deployment validation via global VisualGDB Settings.
at s01.e1(f11 b, List`1 a)
at s01.h1.c(f11 a)
at o72.u`1.g(f11 a)
at VisualGDB.Add_In.Tool_Windows.WPF.DockedProgressPresenter.RunItemizedOperation(Action`1 operation, String caption, ng exceptionHandler, String[] stages)
at o72.y[_ResultType](gh1`1 b, String c, Int32 a, String[] d)
at s01.t1()
trace=[s01.e1:1381, s01+h1.c:0, o72+u`1.g:0, VisualGDB.Add_In.Tool_Windows.WPF.DockedProgressPresenter.RunItemizedOperation:209, o72.y:92, s01.t1:123]

[Lonko]

Dear

 

i have 6 or seven projects like this on my stationary computer it works it opens visualgdb settings file

on my laptop which is a mirror unit it shows this error

 

so why would it work on one pc (vs2013 and vs2019 both work) second pc it does not open??? What is machine specific?

Can we debug and find out? Reluctant to create a new project for each. And i never edited this by hand for sure!

BR

[Lonko]

Dear,

VS Property page does not load for my problematic project. I’m attaching screen shot and my vcxproj file.

 

BR,

 

Attachments:

You must be logged in to view attached files.

[Lonko]

Dear,

 

It works. But would really like to avoid creating a new project. Because on stationary pc it work on laptop it does not. I have tried installing same version on both. Tried installing a trial version to 3rd computer and the project failed to open. Can we debug somehow or enable more logging to see which setting is problematic?

 

BR,

[Lonko]

Nope still the same problem…

Initializing assemblies: 16 msec
Registering factories: 105 msec
E:\yyy\xxx.vcxproj is a VisualGDB project. Loading VisualGDB…
Initializing VisualGDB 5.5.4.3540
Checking fonts/colors: 15 msec
Level 2 initialization: 4733 msec
Checking if a VisualGDB-based project is being loaded…: 5072 msec => Loading VisualGDB
hiding coverage report viewer…
Querying output window style…
showing coverage report viewer…
SysprogsSuggestedActionsProvider: creating tagger for C/C++…
SysprogsSuggestedActionsProvider: Not a CppEngine source. Skipping SuggestedActionsSource creation
RenameHighlightSmartTaggerProvider: creating tagger for C/C++…
RenameHighlightSmartTaggerProvider: creating tagger for Output…
Unexpected exception: Object reference not set to an instance of an object.
—————— System.NullReferenceException ——————
System.NullReferenceException: Object reference not set to an instance of an object.
at ky1.get_MainExecutable()
at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.LookupSettingsFile(fy1 a)
at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel..ctor(fy1 b, Boolean a, x92 c)
at VisualGDB.Common_GUI.Configuration_editors.MultipleProjectPropertiesEditModel.CreateConfigurationModel(fy1 a)
at VisualGDB.Common_GUI.Configuration_editors.MultipleProjectPropertiesEditModel.i(c a)
at VisualGDB.Common_GUI.Configuration_editors.MultipleProjectPropertiesEditModel..ctor(zh2 a, x92 b)
at VisualGDB.Common_GUI.WPF.ProjectPropertiesWindow3..ctor(zh2 prj, Type pageTypeToSelect)
at q7.GDBProjectProperties.ExecuteForProject(q7 addIn, Object objPrj, Type pageTypeToSelect)

[Lonko]

Dear,

 

support paid.

 

BR,

[Lonko]

Hi,

is it possible to set intellisense source cache on local machine with relative paths?

Best regards,

[Lonko]

Dear,

found the problem, it probably clashes with rebuild or clean + build option. In the VGDB project settings I had option “Skip build commands if no source file changes have been detected” ticked, and this is the cause of the problems. The option it self is correct, but the implementation behind should be worked on… What I mean is if no files transferred no build is needed, build is needed ONLY if rebuild or clean + build or clean + rebuild happened.

So doing a build with the thingy checked: (REBUILD, CLEAN+BUILD, CLEAN+REBUILD does not work), below example shows what happens if I do a build on already built solution, where in fact was no changes.
It detects that no files changed = OK, because no files changed skipping build command = OK!
1> VisualGDB: Attempting inline build…
1> VisualGDB: No file changes detected. If you believe it’s a mistake, please clean the project and build it again.
1> No relevant source files have been changed. Skipping build commands.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

With the thingy NOT-checked: (REBUILD, CLEAN+BUILD, CLEAN+REBUILD do work as expected), below example shows what happens if I do a build on already built solution, where in fact was no changes.
It detects that no files changed = OK, because no files changed skipping build command = NOK! so it did a build on the build system even if no change occurred.
1> VisualGDB: Attempting inline build…
1> VisualGDB: No file changes detected. If you believe it’s a mistake, please clean the project and build it again.
1> VisualGDB: Executing prebuild actions
1> VisualGDB: Run “make CONFIG=Debug” in directory “/tmp/VisualGDB/d/_Work/e/Devices/Pay/Pay” on user@192.168.3.207 (SSH) should not happen
1> make: Nothing to be done for `all’.
1> VisualGDB: Executing postbuild actions
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

Hope I have cleared it, it is easily reproducible.

3. When I’ll have the time i’ll check the benchmarks and post it. The option to leave the executable on the build system and mount the filesystem of the target is also very good, is it possible to integrate that option into the VGDB, something like auto-mount target and run executable from there ?
Don’t get me wrong I know how to do it, but i think your product is very appealing to Windows users that like to get into the c++ + embedded world but lack Linux knowledge of scripts, mounts,… i know because i came across some people with same characteristics 🙂

4. The suggested option does not help, it has the same result, please see the logs on you email.
As you said in the email large number of sources are making this, we were planning with another company to re-do the project in VGDB, but that is kind of a stopper as the project has over 100 files, and few 100k lines of code….

5. This happens mainly when something has gone wrong, like the timeout for setting a breakpoint or not killing the debugged program correctly or…. number of things… And again don’t get me wrong 🙂 like i said in point 3. it would be very much more user friendly to have a tick, kill existing gdb server with my debugged program before starting, as you have all the parameters to identify the gdbserver and executable 🙂
Not a request, but a nice feature 🙂

Thank you guys, hope I’m not nagging, but I want show also the windows user side 🙂

Once again fantastic product!
Best regards,

[Lonko]

Dear,

Please see my answers below:

1. What exactly do you mean by nothing happens? What does the Output window say after executing those commands? Please check that the build and clean commands are set in VisualGDB Project Properties. If they look fine, then check the Properties of the project to see if the NMake commands are calling VisualGDB.

Sorry i was mistaken, clean works it deletes the directory where executable is put, but rebuild does not work, this is the output:
1>

Rebuild All started: Project: Pay, Configuration: Debug Win32

1> VisualGDB: Attempting inline build…
1> VisualGDB: Executing preclean actions
1> VisualGDB: Run “make CONFIG=Debug clean” in directory “/tmp/VisualGDB/d/_Work/e/Devices/Pay/Pay” on user@192.168.3.207 (SSH)
1> rm -rf Debug
1> VisualGDB: Executing postclean actions
1> VisualGDB: Attempting inline build…
1> VisualGDB: Executing preclean actions
1> VisualGDB: Run “make CONFIG=Debug clean” in directory “/tmp/VisualGDB/d/_Work/e/Devices/Pay/Pay” on user@192.168.3.207 (SSH)
1> rm -rf Debug
1> VisualGDB: Executing postclean actions
1> VisualGDB: No file changes detected. If you believe it’s a mistake, please clean the project and build it again.
1> No relevant source files have been changed. Skipping build commands.
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

Notice this: No relevant source files have been changed. Skipping build commands. This is if i have Transfer only changed files option! When you do a clean it does not rebuild the executable :S
And after this even if i try to start debugging it says LIBSSH2_ERROR_SCP_PROTOCOL because it cannot find the executable. And the only way to solve this is to go to project options and tick Always transfer all files and then it will build…

(only changed option also does not detect if we move the files around, from one dir to another, that would mean changing all include statements in other files, so it should when any file is moved request a full transfer of all files, so that you can see that there is in some source file a problem because some header file has moved.)

So you VGDB should remember that there was a clean issued or rebuild and transfer all the files again and rebuild!

3. If you need to copy many files, then consider switching to using shared directories instead. You can also disable the file synchronization and use your own synchronization command in pre-build commands.
Not that much than copy many files, than that rsync is a in many cases a lot faster. Like now i’m building a project where executable, because it cannot be striped is around 12mb big, and deployment target is on wifi… Copying is a nightmare 😀 So yes i could mount and run from there, but i tried rsync also… its alot faster. What for the future would be a great thing to do is to put another dialog, what to copy to target and user could enter files/paths that are copied with the deployment

4. We would need to see the full gdb log to be able to tell what the cause is here. Please enable gdb logging on the GDB settings page in VisualGDB Project Properties. Then start debugging, replicate your scenario, stop debugging and give us the gdb log from your project directory.

When app is running and i got to the a source file and press to set the break point in few seconds GDB Command Timeout appears saying it takes too long to complete and from this there is no way back. I usually press abort command which causes SIGINT and the stop the debugging. I will send the log to support email. Thank you

5. This is because sometimes you may want to attach to the running instance instead. Normally when gdb is detached, gdbserver should die together with the app. If this does not happen, add a pre-debug or post-debug command to kill the gdbserver or modify in GDB settings which command should be executed when debugging is stopped.

Ok the script i can write my self, but in the future… it would help to have an option if we don’t attach kill 🙂

[Lonko]

You are correct the cached include folder was not in the NMAKE options!
Now the errors are gone but somehow intellisense sometimes show limits and all the errors in it but that will be survivable 😀

Thank you!

[Lonko]

Hi implemented the vizualizers and it works ok.

Hexadecimals are usualy not displayed on byte arrays. Also sometimes when you have complex data type and in it vector with bytes it ignores the Hexadecimal switch.
Basicaly sometimes it works sometimes it does not 😀

[Lonko]

If you think i can manage to adjust the code so that it will fit my toolchain then please send, as it is really anoying :S
Also is there a way to display vars either in decimal or hex instead of octal ? Can this also be change with visualizers?

Regards,

[Lonko]

in gcc_Debug.h is only #define __STDC_HOSTED__ 1

and no __STDC__ and intellisense does not parse it.
What is more strange is that intellisense does not find some of the header files that are in the local cache.
For example it cannot find #include “svc_uif.h” but compilation goes ok. The file is located in C:UsersUporabnikAppDataLocalVisualGDBRemoteSourceCache192.168.3.207005includesvc_uif.h but for some reason intellisense does not pick up the file!

also in gcc_Debug.h
// — Include directories begin — //
//all includes are commented so no includes listed here!

Also it nags about redefinition of DEBUG

This is the whole gcc_Debug.h
/*
This file is only used by IntelliSense (VisualStudio code suggestion system)
DO NOT INCLUDE THIS FILE FROM YOUR ACTUAL SOURCE FILES.
This file lists the preprocessor macros extracted from your GCC.
It is needed for IntelliSense to parse other header files correctly.
*/
#ifdef _MSC_VER
#define __DBL_MIN_EXP__ (-1021)
#define __FLT_MIN__ 1.17549435e-38F
#define __CHAR_BIT__ 8
#define __WCHAR_MAX__ 2147483647
#define __DBL_DENORM_MIN__ 4.9406564584124654e-324
#define __FLT_EVAL_METHOD__ 0
#define __unix__ 1
#define unix 1
#define __SIZE_TYPE__ unsigned int
#define DEBUG 1
#define __ELF__ 1
#define __DBL_MIN_10_EXP__ (-307)
#define __FINITE_MATH_ONLY__ 0
#define __ARMEL__ 1
#define __GNUC_PATCHLEVEL__ 3
#define __FLT_RADIX__ 2
#define __LDBL_EPSILON__ 2.2204460492503131e-16L
#define __SHRT_MAX__ 32767
#define __LDBL_MAX__ 1.7976931348623157e+308L
#define __linux 1
#define __CHAR_UNSIGNED__ 1
#define __LDBL_MAX_EXP__ 1024
#define __LONG_MAX__ 2147483647L
#define __linux__ 1
#define __unix 1
#define __SCHAR_MAX__ 127
#define __DBL_DIG__ 15
#define __USER_LABEL_PREFIX__
#define linux 1
#define __STDC_HOSTED__ 1
#define __EXCEPTIONS 1
#define __LDBL_MANT_DIG__ 53
#define __FLT_EPSILON__ 1.19209290e-7F
#define __APCS_32__ 1
#define __GXX_WEAK__ 1
#define __LDBL_MIN__ 2.2250738585072014e-308L
#define __WCHAR_TYPE__ long int
#define __FLT_DIG__ 6
#define __FLT_MAX_10_EXP__ 38
#define __INT_MAX__ 2147483647
#define __gnu_linux__ 1
#define __FLT_MAX_EXP__ 128
#define __DECIMAL_DIG__ 17
#define __DBL_MANT_DIG__ 53
#define __WINT_TYPE__ unsigned int
#define __GNUC__ 3
#define __LDBL_MIN_EXP__ (-1021)
#define __arm__ 1
#define __LDBL_MAX_10_EXP__ 308
#define __DBL_EPSILON__ 2.2204460492503131e-16
#define __DBL_MAX__ 1.7976931348623157e+308
#define __cplusplus 1
#define __USING_SJLJ_EXCEPTIONS__ 1
#define __DEPRECATED 1
#define __DBL_MAX_EXP__ 1024
#define __FLT_DENORM_MIN__ 1.40129846e-45F
#define __GNUG__ 3
#define __LONG_LONG_MAX__ 9223372036854775807LL
#define __FLT_MAX__ 3.40282347e+38F
#define __GXX_ABI_VERSION 102
#define __FLT_MIN_10_EXP__ (-37)
#define __FLT_MIN_EXP__ (-125)
#define __GNUC_MINOR__ 3
#define __DBL_MAX_10_EXP__ 308
#define __LDBL_DENORM_MIN__ 4.9406564584124654e-324L
#define __DBL_MIN__ 2.2250738585072014e-308
#define __ARM_ARCH_4T__ 1
#define __PTRDIFF_TYPE__ int
#define __LDBL_MIN_10_EXP__ (-307)
#define __REGISTER_PREFIX__
#define __LDBL_DIG__ 15
#define __NO_INLINE__ 1
#define _GNU_SOURCE 1
#define __FLT_MANT_DIG__ 24
#define __VERSION__ “3.3.4”
#endif

// — Include directories begin — //
///usr/sa/include
///usr/sa/include/mps
///usr/sa/include/uis
///usr/samoa/tools/toolchain/arm-linux-uclibc/include/c++
///usr/samoa/tools/toolchain/arm-linux-uclibc/include/c++/arm-linux-uclibc
///usr/samoa/tools/toolchain/arm-linux-uclibc/include/c++/backward
///usr/samoa/tools/toolchain/lib/gcc-lib/arm-linux-uclibc/3.3.4/include
///usr/samoa/tools/toolchain/arm-linux-uclibc/sys-include
// — Library directories end — //

// — Library directories begin — //
// — Library directories begin — //

[Author]

Posts