very strange memory problem ....please help
-
Hello all Though its linux problem I thought I will give a try to my age old forum as the problem seems to be typical memory management ...ok here I go .. We have a class which has members listed as below in the declaration class SOAP_CMAC MyUserProfile { public: std::string name; std::string name2; std::string firstName; public: LONG64 pwdStatus; std::string setType; public: class NotifyOptions *mNotifyOptions; LONG64 USCOREtype; std::string USCOREmacAddress; std::string USCOREipAddress; public: MyUserProfile() { } virtual ~MyUserProfile() { } }; In the run time after object for MyUserProfile is created , reference to std::strings USCOREmacAddress and USCOREipAddress are crashing due to segmentation fault! The lines which crash due to segmentation fault are doing an assign operation USCOREmacAddress.assign(“char string”); But reference to std::strings name , name2 , firstName and settype do not crash . Upon observation I found that the line class NotifyOptions *mNotifyOptions is in between the two sections . So I moved the line class NotifyOptions *mNotifyOptions ; to the end of the class declaration . This made the reference to name , name2 , firstName , settype also to crash !!! . It seems this object mNotifyOptions which will be created at run time is somehow the reason for the crash happening on std::string objects ….But I am at wits end to know what it is and how to solve it … The point is : we migrated from gcc library 2.4. to 2.6 . And after this this problem surfaced without any modifications in the code present in both situations …. Any help guys on this problem ? with warm regards
redindian
-
Hello all Though its linux problem I thought I will give a try to my age old forum as the problem seems to be typical memory management ...ok here I go .. We have a class which has members listed as below in the declaration class SOAP_CMAC MyUserProfile { public: std::string name; std::string name2; std::string firstName; public: LONG64 pwdStatus; std::string setType; public: class NotifyOptions *mNotifyOptions; LONG64 USCOREtype; std::string USCOREmacAddress; std::string USCOREipAddress; public: MyUserProfile() { } virtual ~MyUserProfile() { } }; In the run time after object for MyUserProfile is created , reference to std::strings USCOREmacAddress and USCOREipAddress are crashing due to segmentation fault! The lines which crash due to segmentation fault are doing an assign operation USCOREmacAddress.assign(“char string”); But reference to std::strings name , name2 , firstName and settype do not crash . Upon observation I found that the line class NotifyOptions *mNotifyOptions is in between the two sections . So I moved the line class NotifyOptions *mNotifyOptions ; to the end of the class declaration . This made the reference to name , name2 , firstName , settype also to crash !!! . It seems this object mNotifyOptions which will be created at run time is somehow the reason for the crash happening on std::string objects ….But I am at wits end to know what it is and how to solve it … The point is : we migrated from gcc library 2.4. to 2.6 . And after this this problem surfaced without any modifications in the code present in both situations …. Any help guys on this problem ? with warm regards
redindian
If you are not getting any additional warning messages from the compiler with 2.6, then I would check to make sure that all modules were being compiled with the new 2.6 library. Delete all the object modules first if you have to.
Best wishes, Hans
-
Hello all Though its linux problem I thought I will give a try to my age old forum as the problem seems to be typical memory management ...ok here I go .. We have a class which has members listed as below in the declaration class SOAP_CMAC MyUserProfile { public: std::string name; std::string name2; std::string firstName; public: LONG64 pwdStatus; std::string setType; public: class NotifyOptions *mNotifyOptions; LONG64 USCOREtype; std::string USCOREmacAddress; std::string USCOREipAddress; public: MyUserProfile() { } virtual ~MyUserProfile() { } }; In the run time after object for MyUserProfile is created , reference to std::strings USCOREmacAddress and USCOREipAddress are crashing due to segmentation fault! The lines which crash due to segmentation fault are doing an assign operation USCOREmacAddress.assign(“char string”); But reference to std::strings name , name2 , firstName and settype do not crash . Upon observation I found that the line class NotifyOptions *mNotifyOptions is in between the two sections . So I moved the line class NotifyOptions *mNotifyOptions ; to the end of the class declaration . This made the reference to name , name2 , firstName , settype also to crash !!! . It seems this object mNotifyOptions which will be created at run time is somehow the reason for the crash happening on std::string objects ….But I am at wits end to know what it is and how to solve it … The point is : we migrated from gcc library 2.4. to 2.6 . And after this this problem surfaced without any modifications in the code present in both situations …. Any help guys on this problem ? with warm regards
redindian
class NotifyOptions *mNotifyOptions; this is only a pointer, which got to get assigned to an object to work with. As mNotifyOptions = new NotifyOptions(); in such strange cases you should watch the memory for changes :cool:
Press F1 for help or google it. Greetings from Germany
-
class NotifyOptions *mNotifyOptions; this is only a pointer, which got to get assigned to an object to work with. As mNotifyOptions = new NotifyOptions(); in such strange cases you should watch the memory for changes :cool:
Press F1 for help or google it. Greetings from Germany
Hi Hans Could you plesae elaborate your point ? I understand the memory will be allocated to the pointer of the class object at runtime . But why and how should it affect the adjacent std::strings ? Also the point I am wondering is that the memory of std::string comes from stack while that of mNotifyOptions is from heap . regards
redindian
-
Hi Hans Could you plesae elaborate your point ? I understand the memory will be allocated to the pointer of the class object at runtime . But why and how should it affect the adjacent std::strings ? Also the point I am wondering is that the memory of std::string comes from stack while that of mNotifyOptions is from heap . regards
redindian
-
Hello all Though its linux problem I thought I will give a try to my age old forum as the problem seems to be typical memory management ...ok here I go .. We have a class which has members listed as below in the declaration class SOAP_CMAC MyUserProfile { public: std::string name; std::string name2; std::string firstName; public: LONG64 pwdStatus; std::string setType; public: class NotifyOptions *mNotifyOptions; LONG64 USCOREtype; std::string USCOREmacAddress; std::string USCOREipAddress; public: MyUserProfile() { } virtual ~MyUserProfile() { } }; In the run time after object for MyUserProfile is created , reference to std::strings USCOREmacAddress and USCOREipAddress are crashing due to segmentation fault! The lines which crash due to segmentation fault are doing an assign operation USCOREmacAddress.assign(“char string”); But reference to std::strings name , name2 , firstName and settype do not crash . Upon observation I found that the line class NotifyOptions *mNotifyOptions is in between the two sections . So I moved the line class NotifyOptions *mNotifyOptions ; to the end of the class declaration . This made the reference to name , name2 , firstName , settype also to crash !!! . It seems this object mNotifyOptions which will be created at run time is somehow the reason for the crash happening on std::string objects ….But I am at wits end to know what it is and how to solve it … The point is : we migrated from gcc library 2.4. to 2.6 . And after this this problem surfaced without any modifications in the code present in both situations …. Any help guys on this problem ? with warm regards
redindian
I would do a search and see if the implementation of malloc was modified between gcc library 2.4 to 2.6. My guess is that if the implementation of malloc changed, memory could be allocated differently using 2.6 over 2.4. You may have already had a memory bug previously using 2.4 but it did not manifest itself until the memory was allocated in some different way using the new library. Apparently somewhere code is overwriting memory in your class corrupting the private contents of the strings or corrupting the internal datastructures of malloc itself. You need to watch the memory locations for the strings to narrow down when the contents of those strings become corrupted. One clarification ... do the seg faults happen only when setting the string value or anytime you use the contents of the string ?
-
Hello all Though its linux problem I thought I will give a try to my age old forum as the problem seems to be typical memory management ...ok here I go .. We have a class which has members listed as below in the declaration class SOAP_CMAC MyUserProfile { public: std::string name; std::string name2; std::string firstName; public: LONG64 pwdStatus; std::string setType; public: class NotifyOptions *mNotifyOptions; LONG64 USCOREtype; std::string USCOREmacAddress; std::string USCOREipAddress; public: MyUserProfile() { } virtual ~MyUserProfile() { } }; In the run time after object for MyUserProfile is created , reference to std::strings USCOREmacAddress and USCOREipAddress are crashing due to segmentation fault! The lines which crash due to segmentation fault are doing an assign operation USCOREmacAddress.assign(“char string”); But reference to std::strings name , name2 , firstName and settype do not crash . Upon observation I found that the line class NotifyOptions *mNotifyOptions is in between the two sections . So I moved the line class NotifyOptions *mNotifyOptions ; to the end of the class declaration . This made the reference to name , name2 , firstName , settype also to crash !!! . It seems this object mNotifyOptions which will be created at run time is somehow the reason for the crash happening on std::string objects ….But I am at wits end to know what it is and how to solve it … The point is : we migrated from gcc library 2.4. to 2.6 . And after this this problem surfaced without any modifications in the code present in both situations …. Any help guys on this problem ? with warm regards
redindian
class SOAP_CMAC MyUserProfile
{
public:
std::string name;
std::string name2;
std::string firstName;
LONG64 pwdStatus;
std::string setType;
class NotifyOptions *mNotifyOptions;
LONG64 USCOREtype;
std::string USCOREmacAddress;
std::string USCOREipAddress;
MyUserProfile() { }
virtual ~MyUserProfile() { }
};void main( void )
{
MyUserProfile mup;
mup.USCOREmacAddress = "1234"; <<--- this crashes?
}"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons