On Mon, Jun 22, 2015 at 05:25:52PM +0200, Patrik Lundin wrote:
>
> I did not see the problem on amd64 or sparc64 at least. I am currently
> building stuff on a fresh macppc snapshot to see what happens there.
> After that I am out of platforms :).
>
So this is interesting. It turns out ods has problems on my macppc as
well. While it does not segfault like it does on i386, the ods-signerd
process instead seems to be spinning forever after the same notify command that
makes it segfault on i386:
---
PID USERNAME PRI NICE SIZE RES STATE WAIT TIME CPU COMMAND
380 _opendns 51 0 11M 7152K run thrslee 4:25 97.12% ods-signerd
---
At the same time i see this in /var/log/daemon that i do not recognize
from before:
---
Jun 24 07:01:46 ns4-old ods-signerd: [adapter] error parsing RR at line 14
(Syntax error, could not parse the RR): \M^?\M^?\M^?\M^?\M^?\M^?\M^?[...]
---
This is the exact same example.com zone file that is available in git:
---
# sha1 example.com
SHA1 (example.com) = 60c5f533184b8cbbbe78ec4c9d455ac3effbd5bf
---
Jérémie: Let me know if you want access to the macppc machine to cross
reference the problems, just send over a public key and I'll set you up.
The summary for now looks like this:
Working: amd64, sparc64
Broken: i386, macppc
Is there some relation between threading and 32/64 bit? It is the main
thing that sticks out currently, since sparc64 rules out an endian issue
as far as i can tell.
--
Patrik Lundin
