Tuesday, March 20th 2018, 8:39am UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.



Date of registration: Oct 12th 2017

Posts: 1


Monday, January 15th 2018, 12:43pm

[ABANDONED] Ozone C++ Class variables shown with only function members


It have now bothered me long enough that I have to ask if someone here have seen the same issue and maybe even have a fix. In my installation of Ozone (actually all installations of Ozone I have had), any watches of class variables is shown only with their function members. If I, however, make a typecast of the address of the class variable to a pointer of the class type in the watch window I can suddenly see the data members of the class (but if the class inherits from other classes I have to make a new pointer to the address shown of the part of the class with the inherited members (ozone shows me this address) to the parent class type to be able to see the data members of the inherited part of the class).

For an example if I have the following code in a cpp file:

C/C++ Source code

class testclasstype
			void setvar(uint32_t val);
			uint32_t getvar(void);
			uint32_t varval;
} ;

testclasstype globaltestinstance;

If I then add a watch to this simply by writing globaltestinstance in the watch window, the watch will only show me the setvar and getvar members, but will, however, show me the address of the instance and the type of the variable. If I instead write "(testclasstype*) 0xDEADBEEF" in the watch window (assuming that 0xDEADBEEF is the address of the class instance), I will see both the setvar and getvar and the varval data member.

Do anyone see the same issue and do someone know a way to fix this?

This post has been edited 2 times, last edit by "andcor" (Jan 15th 2018, 12:49pm)


Super Moderator

Date of registration: Jan 2nd 2017

Posts: 817


Thursday, January 18th 2018, 9:15am


Thank you for your inquiry.
Such an issue is not known to us and it was not reproducible with our testfiles.
What Ozone Version are you currently using?
Could you provide us with an elf file where this issue is reproducible with?

Best regards,