[Bug debug/91751] In backtrace, calls to c++ destructors are shown way afar from the actual place

2019-09-12 Thread Hi-Angel at yandex dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91751 --- Comment #3 from Konstantin Kharlamov --- (In reply to Jonathan Wakely from comment #2) > The advantage of showing the location of the constructor is that you can see > which object is being destroyed. If the location was shown as the end of

[Bug debug/91751] In backtrace, calls to c++ destructors are shown way afar from the actual place

2019-09-12 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91751 --- Comment #2 from Jonathan Wakely --- The advantage of showing the location of the constructor is that you can see which object is being destroyed. If the location was shown as the end of the scope, all local variables would show the same

[Bug debug/91751] In backtrace, calls to c++ destructors are shown way afar from the actual place

2019-09-12 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91751 --- Comment #1 from Andrew Pinski --- I think there are a few dups of this bug. What happens is the call to deconstructor's line is the same as the object line; rather than the end of the scope.