------- Comment #11 from tromey at gcc dot gnu dot org 2006-02-04 02:50 -------
The simplest way to solve the memory leak is to make a new structure
which holds all the data, then allocate an instance of this.
This structure can be allocated with _Jv_AllocBytes, I believe, as the
atable ought to be scanned by the collector (currently anyway).
I have a patch to do this.
In the future, just file a new PR when there is a new bug. Reusing
an existing bug is somewhat weird.
--
tromey at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|thebohemian at gmx dot net |tromey at gcc dot gnu dot
| |org
Summary|memory leak in |memory leak in
|_Jv_Linker::link_symbol_tabl|_Jv_Linker::link_symbol_tabl
|e & ffi usage breaks build |e
|on ARM |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26063
