https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87271
Richard Biener changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87271
--- Comment #4 from rguenther at suse dot de ---
On Wed, 12 Sep 2018, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87271
>
> Jakub Jelinek changed:
>
>What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87271
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87271
--- Comment #2 from Richard Biener ---
I wonder if there's a way to trace all malloc/realloc/free calls as well
(possibly simply via breakpoints and doing continue in their commands, logging
the result).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87271
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|