--- Additional Comments From drow at sources dot redhat dot com 2007-08-06
18:52 ---
HJ suggested this bug should be resolved before 2.18, but that was the day
before the glibc patch was identified.
Could someone explain to me, in small words, how Jakub's patch could cause
this if it
--- Additional Comments From jakub at redhat dot com 2007-08-06 18:59
---
I have posted an unwinder patch in the thread I referenced, see
http://gcc.gnu.org/ml/gcc/2006-12/msg00312.html
but that was without ChangeLog entry, I got no feedback and forgot about it
(because in the meantime
--- Additional Comments From drow at sources dot redhat dot com 2007-08-06
19:38 ---
Oh, I see. Without that unwinder patch, if the PC wasn't saved we'll
end up with a segfault. Since this is coming through Java, I assume
we're getting the unwinder re-invoked from the signal handler,
--
What|Removed |Added
Component|binutils|libc
Product|binutils|glibc
Version|2.18 (HEAD)
--
What|Removed |Added
Status|WAITING |NEW
Last reconfirmed|-00-00 00:00:00 |2007-08-01 11:24:00
date|
