-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segfault of dbd -c #850
Comments
For starters, can you please fill out the Environment section, so that we know the version and OS you’re running this with. I can see two ways forward:
The FAQ has instructions for the latter: https://github.com/Netatalk/netatalk/wiki/Developer-FAQ |
Hi, sorry for the late reply but I haven't had time to deal with the issue lately. gdb backtrace
|
... Sorry, I have closed the issue by mistake |
As additional information: the file that triggers the segfault is in "/shares/Office/Users/<username_hidden>/Library/Recent Servers"
|
@UUVE Would you be able to retry this with the recently released v3.2.0? This release contains two specific patches that address EA metadata handling in libatalk, namely: #513 and #575 It should lead to a more graceful outcome when encountering "invalid" types of metadata, and I'm curious how it will look in your case. |
@rdmark |
@UUVE In case it helps, we now distribute a build-from-source guide as an appendix to the Netatalk manual. See the Debian section here: https://netatalk.io/3.2/htmldocs/compile#build-debian |
Description
As stated in the title i'm continuing experiencing this behaviour of dbd -c on a afp share. The share was created a long time ago in netatalk v2.x on Debin and successively migrated to netatalk 3.x. On shares created with netatalk 3.x I do not experience this problem.
To Reproduce
At this moment I don't know a clear situation that trigger the bug
Expected behavior
As the man of dbd states I would expect that the command convert from AppleDouble = v2 to AppleDouble =ea .
Environment
Logs
2024-04-16T17:42:23.323892+02:00 server1 kernel: [419603.410420] dbd[1987870]: segfault at 6e8 ip 00007f2c2405674f sp 00007ffc681b3190 error 4 in libatalk.so.0.0.0[7f2c24051000+39000] likely on CPU 3 (core 3, socket 0) 2024-04-16T17:42:23.323923+02:00 server1 kernel: [419603.410519] Code: 00 4c 8d 0d 63 45 03 00 50 4c 8d 05 b8 44 03 00 eb ad 48 8b 44 24 08 4c 89 ea 4c 89 f6 bf 02 00 00 00 48 8b 40 08 48 8b 40 18 <48> 8b 88 e8 06 00 00 44 8b 80 e0 06 00 00 e8 4e a9 ff ff 85 c0 74
The text was updated successfully, but these errors were encountered: