Criterion crashes (SIGABRT) when providing own main

Bug #2018156 reported by László Várady
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
criterion (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When providing your own main() function, the Criterion test framework crashes with the following error:

> criterion: Re-entering criterion from a test worker. This is a catastrophic bug, please report it on the issue tracker.
> Bailing out to avoid fork-bombing the system.
> criterion: Could not spawn test instance: Protocol error
> Aborted (core dumped)

More info and reproducer steps:
https://github.com/Snaipe/Criterion/issues/495

This happens because unlike in Debian builds, Ubuntu compiles Criterion with the -Bsymbolic-functions linker flag, which prevents Criterion from finding the user's main function.

Since this functionality is part of Criterion's features, I think disabling the linker flag would be a suitable fix.

description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in criterion (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.