Created attachment 12747 [details]
Xorg.log from a server crashed by killing compiz

Once again, does anyone have a clue why there are no line numbers in my stacktraces? I've compiled with the seemingly redundant CFLAGS -g3 -ggdb -O1 so there should be no lack of debugging information.

(In reply to comment #2)
> Once again, does anyone have a clue why there are no line numbers in my
> stacktraces?

See comment #4 of bug 13391.

Can you still reproduce this bug with current mesa Git master?

(In reply to comment #3)
> (In reply to comment #2)
> > Once again, does anyone have a clue why there are no line numbers in my
> > stacktraces?
> 
> See comment #4 of bug 13391.
> 
> Can you still reproduce this bug with current mesa Git master?
> 

Sorry about the repeated question. Didn't see your response. Any

Anyways, yes, I can still reproduce the problem. There is no change in behavior. Thanks for your work!

What's your method to "kill" compiz? Ctrl-Alt-Backspace, or kill command?

Ben, any response for Gordon's question in comment# 5?

Sorry about the belated response. It used to happen when compiz segfaulted. I'm now on an i965 so I may or may not be able to reproduce. Regardless, I'm struggling even to get compiz to start with all of the recent DRI2 changes recently. I'll see if I can reproduce it when I finally manage to get it running.

(In reply to comment #6)
> Ben, any response for Gordon's question in comment# 5?
> 

It doesn't seem like I can reproduce this anymore (at least on the 965). Marking as fixed.