On Wed, Jan 30 2019, Otto Moerbeek <o...@drijf.net> wrote: > Hi, > > net/powerdns does not work well on sparc64. It is a C++ program that > uses exceptions quite extensively. The case I'm running into is a > unknown item in a config file. The code should catch the exception and > exit gracefully with an proper error message, but instead a catch-all > is being hit: > > Jan 30 13:12:42 Reading random entropy from '/dev/urandom' > Jan 30 13:12:42 Loading '/usr/local/lib/pdns/libgsqlite3backend.so' > Jan 30 13:12:42 This is a standalone pdns > Jan 30 13:12:42 Listening on controlsocket in '/var/run/pdns.controlsocket' > terminate called after throwing an instance of 'PDNSException' > terminate called recursively > Abort trap (core dumped) > > Is C++ exception handling a known broken thing on sparc64? > > Any suggested remedy or should the port just be marked broken for > sparc64? > > On amd64 the config file error is handled correctly.
I've noticed this in the last sparc64 bulk build report: http://build-failures.rhaalovely.net//sparc64/2019-01-10/net/amule,-daemon.log I haven't looked into the details yet. It might be a fluke, or it might support your "exceptions are broken" theory. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE