On Sat, Apr 27, 2013 at 10:10:32PM -0400, Nathan Trapuzzano <[email protected]>
wrote:
> I wanted to make developers aware of a (presumably) rxvt-unicode bug
We are aware of it, but nobody so far has found a way to reproduce it.
> This issue seems to have been narrowed down to using the rxvt-unicode
> with the infinality freetype2 patch.
That's exciting new information - if it only happens with a certain patch,
then I would say, most likely, that's the source of the problems.
> but on my system, the crashes are happening at slightly different
> places. I'm attaching two of my own backtraces.
It's pretty clear from all backtraces that we have seen that something
corrupts memory, causing crashes later. Valgrind *might* help pinpoint the
error (at least, it has a much higher chance than gdb).
However, since we can't reproduce this problem anywhere we tried, there
is pretty little we can do. Especially if it is indeed caused by a
nonstandard patch, which further decreases the chance that this really is
a bug somewhere in urxvt.
And it indeed looks that way, as there are no problems on other systems,
which (presumably) don't apply this nonstandard patch.
In fact, searching for "infinality crashes" in google quickly shows
that people see crash problems with google earth, lotus notes, firefox,
openoffice, wine and then I stopped looking.
So, thank you for this new information, even if it leads to us ignoring
this problem, as, even if there was a bug in urxvt, it would be hard to
detect it in all the crash noise caused by the infinality patches.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
