http://bugs.freedesktop.org/show_bug.cgi?id=10927
--- Comment #7 from [EMAIL PROTECTED] 2007-07-01 03:48 PST ---
(In reply to comment #6)
> The original bug should be fixed in latest git.
>
> However, the SIGABRT problem is a different bug (not sure if it's our fault or
> not).
With
http://bugs.freedesktop.org/show_bug.cgi?id=10927
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://bugs.freedesktop.org/show_bug.cgi?id=10927
--- Comment #5 from [EMAIL PROTECTED] 2007-06-10 15:24 PST ---
Once more, this time with glibc-debuginfo installed. We're getting hit by the
glibc malloc detection stuff.
Program received signal SIGABRT, Aborted.
0x00b2a402 in __kern
http://bugs.freedesktop.org/show_bug.cgi?id=10927
--- Comment #4 from [EMAIL PROTECTED] 2007-06-10 15:17 PST ---
Adding LogMessage()s with the pPixmap address all the way to free() seems to
make the pointer stick around all the way there. I wonder what's up with that.
New backtrace:
http://bugs.freedesktop.org/show_bug.cgi?id=10927
--- Comment #3 from [EMAIL PROTECTED] 2007-06-10 15:15 PST ---
My backtrace isn't quite the same as pq's. His:
#5 0x0061161e in Xfree (ptr=0xc9cc50) at utils.c:1470
#6 0x2ac5fbfa612c in fbDestroyPixmap (pPixmap=0xc9cc50
http://bugs.freedesktop.org/show_bug.cgi?id=10927
--- Comment #2 from [EMAIL PROTECTED] 2007-06-10 13:34 PST ---
I get the same SIGABRT (note, we're no longer talking about the segfault)
backtrace with a standard Fedora 7 install, straight after typing my username
into the gdm usernam
http://bugs.freedesktop.org/show_bug.cgi?id=10927
--- Comment #1 from [EMAIL PROTECTED] 2007-06-10 11:41 PST ---
Finally I had some time to do poking, but somehow I could not get gdb to
understand nouveau_drv.so anymore. Any hints?
Anyway, I found that the following patch for the DDX
