Bug#454212: megahal segfaults as soon as it's launched

2008-02-13 Thread Niko Tyni
On Mon, Feb 11, 2008 at 10:18:37AM +, Neil McGovern wrote: Niko Tyni wrote: Confirmed using etch i386 (though an amd64 processor). Attached output of megahal and strace. The attached patch fixes a stack corruption issue on 64-bit architectures (reading 8 bytes into a 4-byte buffer) and

Bug#454212: megahal segfaults as soon as it's launched

2008-02-13 Thread Laurent Fousse
Hello, * Niko Tyni [Wed, Feb 13, 2008 at 11:08:12AM +0200]: On Mon, Feb 11, 2008 at 10:18:37AM +, Neil McGovern wrote: Niko Tyni wrote: Confirmed using etch i386 (though an amd64 processor). Attached output of megahal and strace. The attached patch fixes a stack corruption issue

Bug#454212: megahal segfaults as soon as it's launched

2008-02-13 Thread Niko Tyni
tag 454212 - unreproducible tag 454212 + patch thanks On Sun, Feb 10, 2008 at 09:21:01PM +0200, Niko Tyni wrote: However, the original problem is on i386 and happens earlier in the initialization code. I can't reproduce it myself, but I think it might well be caused by the sprintf overflow.

Bug#454212: megahal segfaults as soon as it's launched

2008-02-11 Thread Neil McGovern
Niko Tyni wrote: Confirmed using etch i386 (though an amd64 processor). Attached output of megahal and strace. The attached patch fixes a stack corruption issue on 64-bit architectures (reading 8 bytes into a 4-byte buffer) and an off-by-one sprintf overflow in the error and status file name

Bug#454212: megahal segfaults as soon as it's launched

2008-02-10 Thread Niko Tyni
Confirmed using etch i386 (though an amd64 processor). Attached output of megahal and strace. The attached patch fixes a stack corruption issue on 64-bit architectures (reading 8 bytes into a 4-byte buffer) and an off-by-one sprintf overflow in the error and status file name initialization

Bug#454212: megahal segfaults as soon as it's launched

2007-12-11 Thread Laurent Fousse
Hello, * Giuliani Vito, Ivan [Tue, Dec 04, 2007 at 08:57:56PM +0100]: No, it was my first-time installation and trying to remove the ~/.megahal directory doesn't help... Well, I can't reproduce this. This is what I get when I launch megahal for the first time: [EMAIL PROTECTED]:~$ megahal

Bug#454212: megahal segfaults as soon as it's launched

2007-12-04 Thread Laurent Fousse
Hello, * Giuliani Vito, Ivan [Tue, Dec 04, 2007 at 12:41:13AM +0100]: Package: megahal Version: 9.1.1a-3 Severity: grave Justification: renders package unusable megahal segfaults as soon as it's launched, and no command line switch helps (apart from -h). Gdb doesn't help, it can't resolve

Bug#454212: megahal segfaults as soon as it's launched

2007-12-04 Thread Giuliani Vito, Ivan
On Tue, Dec 04, 2007 at 08:51:12PM +0100, Laurent Fousse wrote: Hello, * Giuliani Vito, Ivan [Tue, Dec 04, 2007 at 12:41:13AM +0100]: Package: megahal Version: 9.1.1a-3 Severity: grave Justification: renders package unusable megahal segfaults as soon as it's launched, and no

Bug#454212: megahal segfaults as soon as it's launched

2007-12-03 Thread Giuliani Vito, Ivan
Package: megahal Version: 9.1.1a-3 Severity: grave Justification: renders package unusable megahal segfaults as soon as it's launched, and no command line switch helps (apart from -h). Gdb doesn't help, it can't resolve symbol names: Program received signal SIGSEGV, Segmentation fault.