[armhf] learning switch - OpenFlow15 test fails due to unexpected debug logging
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openvswitch (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Open vSwitch 3.2.0 added the ability to print backtraces in the event of a fatal crash. The commit [0] adding this functionality also added debug logging on startup if a call to libc backtrace() does not provide any frames.
On the systems where armhf packages are built and tested this is the case and as a consequence the build fails.
Test log excerpt:
# -*- compilation -*-
2560. learning-
../../tests/
--- /dev/null 2023-08-22 06:47:35.672268660 +0000
+++ /tmp/openvswitc
@@ -0,0 +1 @@
+2023-08-
stdout:
2560. learning-
Compiling and running this super simple program confirms the behavior in isolation:
#include <stdio.h>
#include <execinfo.h>
#define BACKTRACE_
int
main(int argc, char **argv)
{
int n_frames;
void *frames[
n_frames = backtrace(frames, BACKTRACE_
printf("%d/%d", n_frames, BACKTRACE_
}
0: https:/
Changed in openvswitch (Ubuntu): | |
status: | New → Fix Committed |
This bug was fixed in the package openvswitch - 3.2.0-1
---------------
openvswitch (3.2.0-1) unstable; urgency=medium
* Team upload. fatal-signal- Drop-logging- of-failed- dummy-backtr. patch: Drop
* Update upstream source from tag 'upstream/3.2.0'
* d/p/docs-*: Update patch for #1042358.
* d/p/lib-
unnecessary debug logging to fix armhf build (LP: #2032623).
-- Frode Nordahl <email address hidden> Tue, 22 Aug 2023 10:43:20 +0200