On Sat, Oct 15, 2011 at 12:47:04AM +0200, Michael Büsch wrote: > I'm running two machines (both sid/amd64) with identical tint2 configs (the > attached). > On one machine it crashes and on the other it doesn't.
I can't reproduce it with this config on my box, either. > > Removing the screen results in a tint2 reload. I guess the following > > command also results in a crash of tint2 on your system? > > > > kill -SIGUSR1 `pidof tint2` > > yep. But only on the one machine where it crashes otherwise, too. > The valgrind backtrace is similar. Can you send me a coredump of tint2? You can generate it by enabling core dumps for the running shell: $ ulimit -c unlimited Then start tint2 from the same shell and wait for the crash: $ tint2 [...] Segmentation fault (core dumped) Now there should be a file called core of approximately 1.6M containing the coredump. -- Sebastian
signature.asc
Description: Digital signature
