Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Try to narrow down the error by removing all unnecessary code (object copy, vector access...). Then if the problem really comes from <code>erase</code>, add guards to be sure the indexes are right. Try again with this code:</p> <pre><code>#include &lt;cassert&gt; void DominoCollection::drawDomino( void ) { assert(dominoes.size() != 0 &amp;&amp; "Your vector is empty"); int index = random.nextNumber( dominoes.size() ); assert(index &lt; dominoes.size() &amp;&amp; "Buffer overflow..."); dominoes.erase( dominoes.begin() + index ); } </code></pre> <p>If it still segfaults, the problem comes from the destructor of the class <code>Domino</code>. Look if there is anything fishy there. You can do quick tests by commenting parts of the destructor (or all of it), to know where the problem comes from. Calling <code>erase</code> will call the destructor of <code>Domino</code>.</p> <p>If the destructor is not implemented, it might be a good idea to implement one with an output in it (on <code>cerr</code>, not <code>cout</code>) to know if it gets there or crashes earlier on. Is <code>Domino</code> a derived class? Does it have any other objects in it or only a composition of primitive types?</p> <p><strong>Edit</strong> </p> <p>I went through your code quickly: the problem comes from the assignment operator:</p> <pre><code>Domino &amp; Domino::operator = ( const Domino &amp; d ) { *this = d; } </code></pre> <p>This is <strong>NOT</strong> how it should be written... I let you debug that as an exercise.</p> <p>As for why that is the source of the bug: you said <code>erase</code> crashed but not <code>pop_back</code>. The main difference between the two (implementation difference, not the obvious semantic difference) is that erasing causes all the elements to shift after the ones deleted (using the <code>=</code> operator) because <code>std::vector</code> requires the elements to be stored consecutively. Whereas pop just changes the tail pointer and does not alter the rest of the container.</p>
    singulars
    1. This table or related slice is empty.
    1. POSegmentation fault when calling vector.erase()
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USThibaut
    1. USThibaut
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSegmentation fault when calling vector.erase()
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COha! beat me to it.
      singulars
      1. PO
      1. USCaptain Obvlious
    2. COThanks for your response. Great idea. Unfortunately it still segfaults on `dominoes.erase()` despite passing the assertions :(
      singulars
      1. PO
      1. USJeremy Villegas
    3. COThe destructor class of `Domino` isn't implemented.
      singulars
      1. PO
      1. USJeremy Villegas
 

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