19 Feb
2011
19 Feb
'11
12:47 a.m.
On 02/18/2011 05:36 PM, PICCORO McKAY Lenz wrote:
seem a problem acceding on XCB method, the
xcb_wait_for_reply () handles and so
then crash.. seems taht u links dinamicaly and the binaries asumin and old (or
maibe new) method now diferent on the new XCB api..
please , any suggestions..
Do you know how I could setup valgrind to get a valgrind.log for this crash? I'm
starting trinity from either startx or kdm and I don't see where I would stick
the valgrind call to catch the kdesktop crash without getting reams of unwanted
data.
Any ideas on this? Is it even needed or helpful?
--
David C. Rankin, J.D.,P.E.