the test-gcc-security result depends on a verision of the glibc

Bug #2007544 reported by Pavel Kopylov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QA Regression Testing
Confirmed
Undecided
Unassigned

Bug Description

The test-gcc-security failed on Ubuntu 18.04:

------------- Begin console output -------------
======================================================================
17:25:09 FAIL: test_10_stack_protector (__main__.GccSecurityTest00)
17:25:09 Stack protector
17:25:09 ----------------------------------------------------------------------
17:25:09 Traceback (most recent call last):
17:25:09 File "./test-gcc-security.py", line 151, in test_10_stack_protector
17:25:09 self._test_overflow_handling('stack-protector', 'stack smashing detected', stack_protector=True)
17:25:09 File "./test-gcc-security.py", line 128, in _test_overflow_handling
17:25:09 self.assertEqual(wanted in output, mapping[target], "'%s' %s in output of '%s':\n%s" % (wanted, ['NOT', 'is'][mapping[target]], " ".join(cmd), output))
17:25:09 AssertionError: '*** stack smashing detected ***: ./stack-protector-on terminated
17:25:09 ' is in output of './stack-protector-on strcpy AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA':
17:25:09 *** stack smashing detected ***: <unknown> terminated
-------------- End console output --------------

Here is the answer to why the word "<unknown>" is printed instead of the name of the failed process on Ubuntu18.04: https://unix.stackexchange.com/questions/530524/disable-stack-smashing-detected-unknown-terminated/530545#530545

Related branches

Revision history for this message
Alex Murray (alexmurray) wrote :

Thanks for reporting this - proposed fixes in https://code.launchpad.net/~alexmurray/qa-regression-testing/+git/qa-regression-testing/+ref/update-test-gcc-security-for-lp-2007544 - if you could also test these and provide any feedback that would be great.

Changed in qa-regression-testing:
status: New → Confirmed
Revision history for this message
Pavel Kopylov (pkopylov) wrote :

Great thanks, these fixes work fine. I've tested on Ubuntu16.04, Ubuntu18.04, Ubuntu20.04.

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.