Summary: | dns/powerdns-recursor: Segmentation fault running pdns_recursor on i386 | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | jose.belejo |
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Some People | CC: | fernape, jose.belejo, kevans, tremere |
Priority: | --- | Keywords: | needs-patch, needs-qa |
Version: | Latest | Flags: | tremere:
maintainer-feedback+
koobs: merge-quarterly? |
Hardware: | i386 | ||
OS: | Any | ||
See Also: |
https://github.com/PowerDNS/pdns/issues/4974 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256530 |
Description
jose.belejo
2020-05-18 11:42:19 UTC
I've talked to people upstream and unfortunately it was decided to not look into this issue on i386 by them. See this for reference: https://github.com/PowerDNS/pdns/issues/4974 So unless you or somebody else can supply a patch to fix it I'm afraid I'll have to mark the recursor as broken on i386. (In reply to Ralf van der Enden from comment #1) Hi Ralf, First please let me thank you your concern and trouble you had investigating this subject. Considering PowerDNS team is not willing to invest more time on i386 platform, I believe it doesn't make much sense for me or anyone else to work on a fix for a specific release without any roadmap for this platform. Strangely, or not, PowerDNS is yet supported on Raspberry PI early models that are as you know 32 bits. On the other hand, PowerDNS Authoritive Server seems to work fine on i386. Anyway, no worries about it, although I'm very comfortable to work with PowerDNS recursor, I'll look for another alternative. Thank you once again. Best regards, Jose Belejo @Ralf (Maintainer) If you have reproduced the issue independently, feel free to submit a patch to set BROKEN_i386 (In reply to jose.belejo from comment #2) Upstream mentioned they would welcome a patch to fix it. Perhaps we should get a backtrace of the crash after building boost and powerdns-recursor (at least) with debug symbols (/etc/make.conf: WITH_DEBUG=yes) I've tried (working with people from upstream) to get some useful information using gdb, truss, etc. about the crash. Nothing useful however. Upstream suggested running the recursor through valgrind, but unfortunately that's broken on i386 (and possible other archs as well) in more than one way. In short: I'm at a loss on how to see what's causing the crash (it's 99.9% chance of being related to threading). With the update to 4.3.1 I already set the BROKEN_i386 (committed May 27th 2020). (In reply to Ralf van der Enden from comment #5) If you're interested, you can try building devel/valgrind-devel with D25452[0] applied; I believe this largely fixes 12.1/i386. [0] https://reviews.freebsd.org/D25452 (In reply to Kyle Evans from comment #7) I've managed to compile valgrind-devel using the review you mentioned. However, running the recursor through several tools didn't give me any useful results. I have to confess I'm a noob at using valgrind, but I would have expected memcheck, helgrind or DRD to show me at least one error. Any help would be appreciated in what arguments to pass to valgrind in order to get some decent information from it. Maybe the output from truss for both arch's is useful for somebody more skilled in debugging. I've put both files here: https://www.cainites.net/files/FreeBSD/ Port was marked as broken in ports r536690 Please close this PR. Upstream no longer supports archs with 32 bits time_t. Set NOT_FOR_ARCHS=i386 in PR bug #256530 ^Triage: OBE, see PR 256530. |