[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: icinga2 in stretch-backports: build failures on arm{el,hf}



Hey Chris,

On Thu, Oct 11, 2018 at 05:33:21PM +0100, Chris Boot wrote:
>Hi ARM porter folks,
>
>A few days I uploaded an icinga2 backport, and this has failed to build
>on the 32-bit ARM architectures; it fails to run its test suite.
>Unfortunately it's all C++ and Boost, and that's not something I'm
>familiar with at all.
>
>The normal stretch version seems to build fine, and it builds fine in
>unstable, just my no-change backport (which will be using older Boost
>and compiler versions, naturally).
>
>The logs are:
>
>https://buildd.debian.org/status/fetch.php?pkg=icinga2&arch=armel&ver=2.9.2-1~bpo9%2B1&stamp=1539099705&raw=0

...

20/90 Test #19: base-base_dictionary/remove .............................................***Failed    0.08 sec
Running 1 test case...
unknown location(0): fatal error: in "base_dictionary/remove": memory access violation at address: 0x000026f8: no mapping at fault address
/<<PKGBUILDDIR>>/test/base-dictionary.cpp(128): last checkpoint

Memory corruption? It's trying to dereference something at an invalid address.

>https://buildd.debian.org/status/fetch.php?pkg=icinga2&arch=armhf&ver=2.9.2-1~bpo9%2B1&stamp=1539104021&raw=0

And a whole load more invalid addresses, NULL pointers this time from
the debug messages:

...
1/90 Test  #3: base-base_array/resize ..................................................***Failed    0.35 sec
Test setup error: memory access violation at address: 0x00000000: no mapping at fault address

      Start  5: base-base_array/remove
 2/90 Test  #2: base-base_array/getset ..................................................***Failed    0.36 sec
Test setup error: memory access violation at address: 0x00000000: no mapping at fault address

 3/90 Test  #5: base-base_array/remove ..................................................***Failed    0.05 sec
Test setup error: memory access violation at address: 0x00000000: no mapping at fault address

 4/90 Test  #1: base-base_array/construct ...............................................***Failed    0.42 sec
Test setup error: memory access violation at address: 0x00000000: no mapping at fault address

 5/90 Test  #4: base-base_array/insert ..................................................***Failed    0.39 sec
Test setup error: memory access violation at address: 0x00000000: no mapping at fault address
...

I'd start by digging into the code in "base" to see what it's doing
with memory. Yet I can see that other builds are fine (e.g. 2.9.2-1 in
unstable). An optimisation problem maybe?

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
  Armed with "Valor": "Centurion" represents quality of Discipline,
  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
  concord the digital world while feeling safe and proud.


Reply to: