On Jun 21, 2012, Uros Bizjak ubiz...@gmail.com wrote:
Hello!
During htab_delete (dropped_values), loc_exp_dep_pool
allocated objects might be accessed, so it is better to free the
pool afterwards.
Bootstrapped/regtested on i686-linux, ok for trunk?
Looks obvious.
The patch doesn't
Hi!
During htab_delete (dropped_values), loc_exp_dep_pool
allocated objects might be accessed, so it is better to free the
pool afterwards.
Bootstrapped/regtested on i686-linux, ok for trunk?
2012-06-21 Jakub Jelinek ja...@redhat.com
PR debug/53706
* var-tracking.c
On Thu, Jun 21, 2012 at 8:15 AM, Jakub Jelinek ja...@redhat.com wrote:
Hi!
During htab_delete (dropped_values), loc_exp_dep_pool
allocated objects might be accessed, so it is better to free the
pool afterwards.
Bootstrapped/regtested on i686-linux, ok for trunk?
Looks obvious.
Thanks,
Hello!
During htab_delete (dropped_values), loc_exp_dep_pool
allocated objects might be accessed, so it is better to free the
pool afterwards.
Bootstrapped/regtested on i686-linux, ok for trunk?
Looks obvious.
The patch doesn't fix all writes to freed up memory, please see
comment #8