Destructor being called on SGI hash_map key

I'm using the hash_map that comes with gcc 4.0 (i.e. <ext/hash_map>) and I have no idea why the destructor is being called on a key object.

I have a class object for which I've defined a hash function and a destructor. Then when I

Code:

---

some_class sc;
hash_map<sc, whatev, hash<sc> > hm;
hm[sc] = yadayada;

---

the destructor is called on sc. I found this because my program would crash due to some_class::~some_class() being called twice. Since ~some_class() frees a dynamic member within, calling it twice will obviously cause a crash.

I went through the code of ext/hash_map and I couldn't find a place where a destructor would be called after hashing the key value. Does anyone have any ideas?

Code:

---

some_class sc;
hash_map<sc, whatev, hash<sc> > hm;
hm[sc] = yadayada;

---

Am I on "Candid Camera" or do you honestly expect to get any help at all posting crap like that?

Soma

Quote:

---

Originally Posted by phantomotap

Am I on "Candid Camera" or do you honestly expect to get any help at all posting crap like that?

---

Yes, you are. Smile. (Do you honestly expect a civilized answer responding with crap like that?)

some_class probably doesn't have a copy constructor and/or assignment operator.

It's never really a question of why is my copy-constructor / assignment-operator / destructor being called in cases like this. The problem is always that you haven't followed the "rule of three":
If you must implement any of the above, then you need to implement all three. Alternatively you may disable copy-construction or assignment by defining then as private and leaving them unimplemented.

Failure to follow the rule of three or disable copy-construction and assignment, is noted as a bug in anything I code review.

If you want specific help on how to implement these then you'll have to post your real class definition.