On Mon, Nov 09, 2009 at 10:17:51PM +0100, Josip Rodin wrote: > On Sat, Nov 07, 2009 at 08:17:04PM +0100, Josip Rodin wrote: > > On Sat, Nov 07, 2009 at 07:43:00PM +0100, Bill Allombert wrote: > > > Package: xvier > > > Version: 1.0-7.4 > > > Severity: grave > > > > > > Hello Josip, > > > > > > This is on lenny-amd64: > > > xvier crash when clicking on the fourth row with > > > "xvier: read from xvier_prog failed" > > > > Hmm, it's actually randomly crashing, I've reproduced it. > > It works on 32-bit (i386), but reliably crashes in xvier_prog on 64-bit. The > upstream is MIA, and my C is a bit rusty, so it'll take me a while to get > the proper hang of this. The X part of the program talks via stdin/stdout to > xvier_prog which it first forks, so I need to find a way to run that child > in gdb so that I can see where it crashes. Its fprintf(stderr, ...) goes > nowhere currently, it seems.
> This old code has various malloc() calls misdeclared which causes the > compiler to complain a lot, so I'm guessing this might be something > reasonably trivial like systematic mishandling of the value of int... Adding #include <unistd.h> #include <string.h> #include <stdlib.h> to all the C files seeam to chut up most warnings... Cheers, Bill. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
