Bug#788651: Some more info

2015-09-15 Thread Guilhem Bonnefille
Hi Robert, I think something went wrong when you sent your email, because I don't see the attached GDB output. And I don't understand: is the bug still there? Or it disapeared after a libnettle upgrade? On Mon, 15 Jun 2015 20:51:37 +0200 Robert Latest wrote: > Hello

Bug#788651: Some more info

2015-06-15 Thread Robert Latest
Hello Bernd, this seems to be something within the initialization code of libnettle. See attached text file of gdb's output. I just updated/upgraded again, and the error went away. Thanks! robert On Sun, 14 Jun 2015 10:17:19 +0200 Bernd Zeimetz be...@bzed.de wrote: Hi Robert, you could

Bug#788651: Some more info

2015-06-14 Thread Robert Latest
Hello viking maintainer, I just did a very primitive test. I downloaded the Debian viking source and built it natively on my system. Still segfaults. Then I replaced main() with a primitive two-liner (see below), and it still segfaults. So the error is within some start-up code or linker

Bug#788651: Some more info

2015-06-14 Thread Bernd Zeimetz
Hi Robert, you could eithe rtry to run it within gdb and get a backtrace and/or look at the output of dmesg, sometimes it says which library is the reason of your issues or whats going on. From my experience running memtest might be an idea, too :) cheers, bernd On 06/14/2015 10:10 AM,