https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28859
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> --- On Mon, 17 Jul 2017, marxin at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28859 > > Martin Liška <marxin at gcc dot gnu.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEW > Last reconfirmed| |2017-07-17 > Ever confirmed|0 |1 > > --- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> --- > Do I understand it that practically impossible to handle that as we would have > to somehow detect all malloc-family functions triggered after a crash_signal > is > executed? > > In case of PR81382 we either need to have layout class not containing of types > that can possibly allocate a memory via malloc, or we can have an env variable > that will prevent displaying of locations if crash_signal happened? Would it > be > welcomed one of there approaches? I think it's just not possible to easily do sth here, so we shouldn't care too much IMHO.
