Now xcb discarted! �_�u (uff what a problem!!!) What version of libc6 (glibc) do u have? On Sun, Feb 20, 2011 at 2:51 PM, David C. Rankin <drankinatty@...> wrote: > On 02/18/2011 06:47 PM, David C. Rankin wrote: >> 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? >> > > Here is an updated kcrash after rebuilding libxcb with 'export CFLAGS="$CFLAGS > -g"' and 'export CXXFLAGS="$CXXFLAGS -g"' > > Could this be further up in libc? > > -- > David C. Rankin, J.D.,P.E. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: trinity-devel-unsubscribe@... > For additional commands, e-mail: trinity-devel-help@... > Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ > Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting > -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; http://shutendouji.net creador de massenkoh linux.