Databases
StackOverflow2013
Postsdbo
POFailed to create object of derived class in some cases
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFailed to create object of derived class in some cases
    primarykey
    data
    text
    <pre><code>// Base Class class Base { public: void RegisterWithServer(); // some more functions protected: Base(std::string aTestName, std::string aServerName); ~Base(); private: std::string mString; std::string mServerName; yami::agent mYAMIAgent; }; // Base Class constructor Base::Base(string aTargetName, string aServerName): mString(aTargetName), mServerName(aServerName) { // my debug statment cout &lt;&lt;" we are in Base Class constructor"&lt;&lt; std::endl; cout &lt;&lt;" in normal case we get this debug statement but in case of crash it doesnt reach till here I suppose "&lt;&lt; endl; } // DerivedClass class derivedClient: public Base { public: derivedClient(std::string aceptedString); virtual ~derivedClient(); private: std::string mServerAddress; std::string mServerName; }; // constructor derivedClient::derivedClient(string aceptedString): Base(aceptedString, "ServerTest"), mServerAddress(aceptedString), mServerName ("ServerTest") { cout &lt;&lt;" in normal case we get this debug statement but in case of crash it doesnt reach till here I suppose "&lt;&lt; endl; RegisterWithServer(); // call base class function }; // in some other function in different file some function() { ..... ..... try { if( meet certain condition) { ...... ...... cout &lt;&lt;" the code reached till here" &lt;&lt; std::endl; derivedClient dClient("192.168.2.110");// problem ?? cout &lt;&lt;"in case of crash below lines are not printed nor any message is printed from both constructors "&lt;&lt; std::endl; } } catch( const yami::yami_logic_error &amp; aYamiException) { cout &lt;&lt; "error: " &lt;&lt; aYamiException.what() &lt;&lt; endl; } } </code></pre> <p>Hi Guys,<br> I am fixing the bug in the existing software .<br> Problem -> after some times the software stops responding . What I have done -> I have traced the problem and found that when software crashes it fails before the object creation from dervived class. </p> <p>The derived class calls dervived constructor and base constructor. I have added debug statement and found nothing is printed on debug. </p> <p>I want to know why the code is not even going into derived class and base class ? is it possible that private variables have not been initialsed properly ? </p> <p>Please throw some comments on sample code.<br> Thanks and regards,<br> Sam </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USsamantha
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. CO`RegisterWithServer()` - Looks suspicious.
      singulars
      1. POFailed to create object of derived class in some cases
      1. USEd S.
    2. COThe problem is almost certainly something to do with `yami::agent`. This will be constructed before the body of `Base::Base` or `derivedClient::derivedClient` is run.
      singulars
      1. POFailed to create object of derived class in some cases
      1. USOliver Charlesworth
    3. CORegisterWithServer() when called from derived constructor creats yamiagent. example //register the subscription for incoming messages mYAMIAgent.register_object(mServerrName + ".Subscriber", *this);
      singulars
      1. POFailed to create object of derived class in some cases
      1. USsamantha
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload