------- Comment #2 from drow at gcc dot gnu dot org 2010-02-12 15:52 ------- The type of the class only contains one destructor. If you have to pick one for a debugger to call, in-charge makes the most sense. For other debugger purposes they all make equal sense (or nonsense).
If you want to represent all three in the debug info, then not only do we need to know that they are clones of the same function, we also need to know which one is the in-charge versus not-in-charge versus deleting destructor to call the right one for debugger implementation of the delete statement. I'm pretty sure that would require new debug info extensions and new debugger support. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37237
