"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
Note that it's an assert ... that means that it's a policy
decision by
the people who wrote the interpreter. I presume it was their judgment
that this is a sufficiently bizarre event that they couldn't think of
a reasonable defensive action to take to stabilize XEmacs. Eg, if the
stack or the Emacs code itself got smashed by some wild pointer bug,
then you're in big trouble anyway.
yes I see. true...
That's unlikely to work properly, unless you can reproduce
exactly the
architecture and optimization flags used by the package. I don't
think it's worth the effort.
Actually I did find a debuginfo package (thanks Ville!) [it's not in a
yum repository but I found it on rpmfind] but I agree, I don't think
it's worth the effort.
If it happens again after I remove gnus from site-packages, I'll come
back to this and get more info for you with an unstripped binary.
Best regards,
--
Eric Hendrickson Albedo Applications, Inc.
http://www.crystalcave.net/~edh/ edh(a)mr.net
Don't anthropomorphize computers. They don't like it.