This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/14963] segfault on startup


https://sourceware.org/bugzilla/show_bug.cgi?id=14963

Jakub Jelinek <jakub at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at redhat dot com

--- Comment #12 from Jakub Jelinek <jakub at redhat dot com> ---
Unfortunately even the second patch is incorrect, at least when the *_callback
APIs are used, the demangler is not supposed to use any malloc/free.  Can the
amount of total needed memory for this be determined e.g. at the time when the
component tree is created, so that cplus_demangle_print_callback would then
just alloca all the memory needed for that at once before calling d_print_comp?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]