Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1554276 - clang frontend command failed due to signal
Summary: clang frontend command failed due to signal
Keywords:
Status: CLOSED DUPLICATE of bug 1554280
Alias: None
Product: Fedora
Classification: Fedora
Component: clang
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom Stellard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-12 10:04 UTC by Stas Sergeev
Modified: 2018-03-16 18:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-16 18:33:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
test-case (836 bytes, text/x-csrc)
2018-03-12 10:04 UTC, Stas Sergeev 		no flags Details
View All

Description Stas Sergeev 2018-03-12 10:04:17 UTC 
Created attachment 1407134 [details]
test-case

Description of problem:
clang crash with the attached test-case

Version-Release number of selected component (if applicable):
clang-5.0.1-1.fc27.x86_64

How reproducible:
easily

Steps to Reproduce:
1. clang++ -std=c++11 -c malloca.cpp

Actual results:
clang-5.0: error: unable to execute command: Segmentation fault (core dumped)

Expected results:
proper error messages (the code is clearly invalid)

Additional info:
This code is actually a result of the question I asked here:
https://stackoverflow.com/questions/48915888/allocate-shared-with-malloc
Maybe someone from clang devs/C++ gurus can hint me about
why do I need to manually override the delete operator here?
Comment 1 Tom Stellard 2018-03-16 18:33:09 UTC 
Same root cause as bug 1554280.

*** This bug has been marked as a duplicate of bug 1554280 ***
Comment 2 Tom Stellard 2018-03-16 18:42:19 UTC 
Also, you'll have to ask your C++ question somewhere else, I'm not sure of the answer.
Note You need to log in before you can comment on or make changes to this bug.