https://bugzilla.novell.com/show_bug.cgi?id=283914#c21 --- Comment #21 from Stefan Dirsch <sndirsch@novell.com> 2007-08-26 02:23:07 MST ---
Upstream bugreport:
------- Comment #1 From Bart Massey 2007-08-24 17:46:48 PST [reply] ------- I've managed to reproduce the bug, at least, but I really am pretty swamped right now and really don't have time to debug it myself. I note that xv makes a bunch of Xlib API calls from its signal handler. As far as I can recall this is technically illegal in Xlib; furthermore I'm pretty sure it will cause trouble in Xlib/XCB. My guess is that the malloc pool is getting corrupted: Xlib/XCB uses malloc pretty heavily, and Xlib basically doesn't use it, so this may be the difference? ------- Comment #2 From Bart Massey 2007-08-25 16:21:30 PST [reply] ------- I checked with Keith Packard, and he says that he is surprised old Xlib would put up with the calls from an interrupt handler either---this definitely isn't supposed to work. This sure seems likely to be an xv bug to me, triggered by the greater use of malloc in Xlib/XCB. I'm marking it NOTOURBUG until someone convinces me it is, I'm afraid. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.