serious(?) glibc backtrace() problem on IA64

[Boehm, Hans]

> From: Andrew Haley [mailto:aph@cambridge.redhat.com]
>  > Is this fixed in other versions of glibc?  Should the 
> libjava configury
>  > stuff explicitly turn off HAVE_BACKTRACE? 
> 
> That sounds right.
> 
>  > If so, can an autoconf expert add that hack to at least the 3.1
>  > tree?
None seems to have spoken up, so how's the attached branch from a nonexpert?
I definitely want this in the branch; I'm less sure about the trunk.  If
it's approved, I would also appreciate a volunteer to regenerate configure
after I check it in, since I'm not sure I have the right version of
autoconf.
> 
>  > In the longer term, if this is still in glibc, it seems to 
> me that this is
>  > the wrong default for backtrace() on IA64.
> 
> I would prefer to use libunwind, to begin with for IA-64, and later
> for everything.
> 
No disagreement here.  I didn't state that quite right originally.  I think
one way or another, the current "generic" version of backtrace in glibc
should be disabled for IA64.  (Other platforms may have similar issues.)  An
implementation that fails in random ways seems to be the worst possible
placeholder.

Hans

-------------- next part --------------
A non-text attachment was scrubbed...
Name: backtrace.diff
Type: application/octet-stream
Size: 891 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/java/attachments/20020418/0bd23cd9/attachment.obj>