On 08/03/2016 09:03 PM, Petter Reinholdtsen wrote: > Thank you. I just tested on a Raspberry Pi using the gnupg2/scdaemon > version 2.1.14-2 in Debian experimental, and this now segfaults when I > try 'gpg2 --card-status'. But for some reason I can't get info from > valgrind, so here is the backtrace from gdb: > > Program received signal SIGSEGV, Segmentation fault. > 0xb6cbc020 in strlen () from /lib/arm-linux-gnueabihf/libc.so.6 > (gdb) bt > #0 0xb6cbc020 in strlen () from /lib/arm-linux-gnueabihf/libc.so.6 > #1 0x7f5b2174 in ?? () > Backtrace stopped: previous frame identical to this frame (corrupt stack?) > (gdb)
arm-linux-gnueabihf ? Your original report says "armel" in the subject. According to https://wiki.debian.org/RaspberryPi, it seems armel. > But I do not quite understand why the old code should work on amd64 but > not on arm. I don't think architecture matters. IIUC, the problem is Raspberry Pi specific, reader specific, or the combination of board and reader. Please note that it works both on armel and armhf on my environment with Gnuk Token and some other readers. --
