Summary: | net-fs/netatalk-2.0.3-r4 segfaults with libc calls for glibc-2.10.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mark A Rada <marada> |
Component: | [OLD] Server | Assignee: | Network Filesystems <net-fs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | axiator, esigra |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 300218 | ||
Bug Blocks: | 289342 |
Description
Mark A Rada
2009-10-07 20:45:40 UTC
Please try to get a "meaningfull backtrace" http://www.gentoo.org/proj/en/qa/backtraces.xml Hmm, I'm having difficulty, the link you gave isn't helping enough and a bit of googling isn't working too well either. I only get: # gdb /usr/sbin/afpd GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu"... (gdb) run Starting program: /usr/sbin/afpd [Thread debugging using libthread_db enabled] Program exited normally. (gdb) run Starting program: /usr/sbin/afpd [Thread debugging using libthread_db enabled] afpd is already running (pid = 6107), or the lock file is stale. Program exited with code 03. (gdb) thread apply all bt full No registers. (gdb) I also tried a core dump, but have no idea where it ended up (if anywhere). I'll try again later when I have more time, but I am not too sure what I am doing. I can give more details about the conditions under which to cause the bug; it happens when I try to authenticate from my client (MBP OS X.6), the client fails to authenticate after a long pause and then about a minute or two later I can check the server to find the above mentioned conditions. Okay, I give up, I don't have the time for this right now or in the near future. Someone please help! the core dump ends up in the working dir (if it's created). look at the pid's cwd symlink via /proc/<pid>/cwd. re-open if netatalk-2.0.5 doesnt work |