Public bug reported:

epics-base 7.0.8.1+dfsg1-10 has been stuck in stonking-proposed for ~148
days: missing builds on amd64, amd64v3 and arm64.

https://launchpad.net/ubuntu/+source/epics-
base/7.0.8.1+dfsg1-10/+build/32854724

Many database tests abort with "*** buffer overflow detected ***:
terminated" (linkInitTest, asyncSoftTest, longoutTest, printfTest,
analogMonitorTest, scanEventTest, regressTest, asyncproctest,
testCaProvider).

Backtrace (reproduced in a stonking chroot):

  #5  __chk_fail ()
  #6  strcpy (...) at bits/string_fortified.h:93
  #7  dbAllocRecord (...) at ../dbStatic/dbStaticRun.c:125
  #8  dbCreateRecord (...) at ../dbStatic/dbStaticLib.c:1441

dbAllocRecord allocates offsetof(dbCommonPvt, common) + rec_size and
then writes the record fields through precord = &ppvt->common; with
_FORTIFY_SOURCE=3 (Ubuntu's default level) the dynamic object size
checks treat writes past sizeof(dbCommon) as overflows. Debian builds
with level 2 and is fine (7.0.8.1+dfsg1-10 is in testing).

Fix: build with _FORTIFY_SOURCE=2 (DEB_CPPFLAGS_MAINT_APPEND =
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2). In a local build all the buffer
overflow aborts are gone; the remaining failures there were network
tests (no network in that build environment), which pass on Launchpad.
Being verified with a PPA build.

The ppc64el/s390x failures ("No rule to make target
'configure/os/CONFIG..Common'") are unsupported architectures and don't
block migration (no binaries in release).

** Affects: epics-base (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: ftbfs update-excuse

** Tags added: update-excuse

** Tags added: ftbfs

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2170810

Title:
  epics-base FTBFS: tests abort with buffer overflow detected under
  _FORTIFY_SOURCE=3 (dbAllocRecord)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/epics-base/+bug/2170810/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to