this has been reported + fixed on the shadow mailing list. it's memory
corruption on any platform, but doesn't always crash.
http://lists.alioth.debian.org/pipermail/pkg-shadow-devel/2012-February/009159.html
http://lists.alioth.debian.org/pipermail/pkg-shadow-devel/2012-March/009196.html
-mike
Am Mittwoch, 18. April 2012, 01:23:19 schrieb Mirosław Zalewski:
> Hi
Hi Mirosław,
> Just wanted to note, that most likely this bug is architecture-dependent. I
> am using amd64 Debian testing and I was unable to reproduce this issue. So
> was another Debian amd64 user. On Polish unofficial Debia
Hi
Just wanted to note, that most likely this bug is architecture-dependent. I am
using amd64 Debian testing and I was unable to reproduce this issue. So was
another Debian amd64 user. On Polish unofficial Debian forum I have read
reports
that i386 users got segfaults. At least reporter of thi
Hello, I've experienced same problem, however not on Debian. It started
happening since shadow 4.1.5 upgrade (I think).
(gdb) run test
Starting program: /usr/sbin/userdel test
Program received signal SIGSEGV, Segmentation fault.
0xb7e11b59 in vfprintf () from /lib/libc.so.6
(gdb) bt
#0 0xb7e11
4 matches
Mail list logo