Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

2022-01-23 Thread Ondřej Surý
Control: forwarded -1 https://gitlab.isc.org/isc-projects/bind9/-/issues/3108

Yeah, there was wrong assumption on our side that the call would either not 
exist or always return valid value. There’s already MR for it which needs to be 
reviewed as I prepared it over the weekend.

Ondrej
--
Ondřej Surý  (He/Him)

> On 23. 1. 2022, at 23:18, Chris Hofstaedtler  wrote:
> 
> Package: bind9-dnsutils
> Version: 1:9.17.22-1
> Severity: serious
> X-Debbugs-Cc: p...@packages.debian.org
> 
> Dear ISC BIND Maintainers,
> Hello Ondřej,
> 
> src:pdns uses dig in its build to test pdns_server. On ppc64el this
> apparently now crashes:
> 
>  + dig -p 5301 @127.0.0.1 smoke.bind.example.org
>  + tee /tmp/tmp.RRMQ1Z4fs4
>  os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed
> 
> Full pdns build log here:
>  
> https://buildd.debian.org/status/fetch.php?pkg=pdns=ppc64el=4.5.3-1=1642956562=0
> 
> It feels like, if this crashes on an arch, it would crash regardless of
> the supplied parameters, etc.
> 
> The RUNTIME_CHECK was introduced in upstream commit
>  
> https://gitlab.isc.org/isc-projects/bind9/-/commit/4f78f9d72a5dc3f6a596251e662d00cb80cd5e6d
> as I am sure you know :-)
> 
> Thanks,
> Chris


Processed: Re: Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

2022-01-23 Thread Debian Bug Tracking System
Processing control commands:

> forwarded -1 https://gitlab.isc.org/isc-projects/bind9/-/issues/3108
Bug #1004271 [bind9-dnsutils] os.c:84: fatal error: RUNTIME_CHECK((size_t)s == 
(size_t)64) failed
Ignoring request to change the forwarded-to-address of bug#1004271 to the same 
value

-- 
1004271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

2022-01-23 Thread Debian Bug Tracking System
Processing control commands:

> forwarded -1 https://gitlab.isc.org/isc-projects/bind9/-/issues/3108
Bug #1004271 [bind9-dnsutils] os.c:84: fatal error: RUNTIME_CHECK((size_t)s == 
(size_t)64) failed
Set Bug forwarded-to-address to 
'https://gitlab.isc.org/isc-projects/bind9/-/issues/3108'.

-- 
1004271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

2022-01-23 Thread Chris Hofstaedtler
Control: affects -1 src:pdns

* Chris Hofstaedtler  [220123 23:18]:
> It feels like, if this crashes on an arch, it would crash regardless of
> the supplied parameters, etc.

Indeed, on the ppc64el porterbox:

...
Unpacking bind9-dnsutils (1:9.17.22-1) ...
...

(sid_ppc64-dchroot)zeha@perotto:~$ dig
os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed
Aborted
(sid_ppc64-dchroot)zeha@perotto:~$

Chris



Processed: Re: Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

2022-01-23 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 src:pdns
Bug #1004271 [bind9-dnsutils] os.c:84: fatal error: RUNTIME_CHECK((size_t)s == 
(size_t)64) failed
Added indication that 1004271 affects src:pdns

-- 
1004271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1004271: os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

2022-01-23 Thread Chris Hofstaedtler
Package: bind9-dnsutils
Version: 1:9.17.22-1
Severity: serious
X-Debbugs-Cc: p...@packages.debian.org

Dear ISC BIND Maintainers,
Hello Ondřej,

src:pdns uses dig in its build to test pdns_server. On ppc64el this
apparently now crashes:

  + dig -p 5301 @127.0.0.1 smoke.bind.example.org
  + tee /tmp/tmp.RRMQ1Z4fs4
  os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed

Full pdns build log here:
  
https://buildd.debian.org/status/fetch.php?pkg=pdns=ppc64el=4.5.3-1=1642956562=0

It feels like, if this crashes on an arch, it would crash regardless of
the supplied parameters, etc.

The RUNTIME_CHECK was introduced in upstream commit
  
https://gitlab.isc.org/isc-projects/bind9/-/commit/4f78f9d72a5dc3f6a596251e662d00cb80cd5e6d
as I am sure you know :-)

Thanks,
Chris