gcc 5.4 Segmentation fault while making Vulkan 1.0.61.1 example

Bug #1720964 reported by SunBear
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gcc-5 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I am using Ubuntu 16.04 with kernel 4.10.0-33-generic and gcc version 5.4.0-6ubuntu1~16.04.4. I did a local install of Vulkan 1.0.61.1 and tried to build and make one of it's example with the following commands:

cd examples
cmake -H. -Bbuild
cmake -H. -Bdbuild -DCMAKE_BUILD_TYPE=Debug
make -C build
make -C dbuild

During "make -C build" command, I encountered an error that asked me to make a full bug report.
How can I overcome the issue?

$ make -C build
make: Entering directory '$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'
make[1]: Entering directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'
make[2]: Entering directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'
Scanning dependencies of target vulkaninfo
make[2]: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'
make[2]: Entering directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'
[ 10%] Building C object CMakeFiles/vulkaninfo.dir/vulkaninfo.c.o
[ 20%] Linking C executable vulkaninfo
make[2]: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'
[ 20%] Built target vulkaninfo make[2]: Entering directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'
[ 30%] Generating cube-frag.spv
[ 40%] Generating cube-vert.spv Scanning dependencies of target cubepp
make[2]: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'
make[2]: Entering directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'
[ 50%] Building CXX object CMakeFiles/cubepp.dir/cube.cpp.o
In file included from '$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/cube.cpp:39:0: '$HOME/Vulkan/VulkanSDK/1.0.61.1/x86_64/include/vulkan/vulkan.hpp:18745:11: internal compiler error: Segmentation fault && ( maxTessellationGenerationLevel == rhs.maxTessellationGenerationLevel ) ^
Please submit a full bug report, with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
CMakeFiles/cubepp.dir/build.make:72: recipe for target 'CMakeFiles/cubepp.dir/cube.cpp.o' failed
make[2]: *** [CMakeFiles/cubepp.dir/cube.cpp.o] Error 1
make[2]: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build' CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/cubepp.dir/all' failed
make[1]: *** [CMakeFiles/cubepp.dir/all] Error 2
make[1]: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory ''$HOME/Vulkan/VulkanSDK/1.0.61.1/examples/build'

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

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

Changed in gcc-5 (Ubuntu):
status: New → Confirmed
Revision history for this message
madtom1999 (tompotts) wrote :

While building Tensorflow I get this:
ERROR: /home/tom/Programming/tensorflow/tensorflow/contrib/bigtable/BUILD:53:1: C++ compilation of rule '//tensorflow/contrib/bigtable:python/ops/_bigtable.so' failed (Exit 1)
In file included from ./tensorflow/contrib/bigtable/kernels/bigtable_lib.h:23:0,
                 from tensorflow/contrib/bigtable/kernels/bigtable_scan_dataset_op.cc:16:
./tensorflow/core/framework/dataset.h: In destructor 'tensorflow::DatasetIterator<tensorflow::{anonymous}::BigtableScanDatasetOp::Dataset>::~DatasetIterator()':
./tensorflow/core/framework/dataset.h:565:7: internal compiler error: Segmentation fault
 class DatasetIterator : public DatasetBaseIterator {
       ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.

Revision history for this message
Matthias Klose (doko) wrote :

please provide the preprocessed source and the command line options passed to GCC

Changed in gcc-5 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gcc-5 (Ubuntu) because there has been no activity for 60 days.]

Changed in gcc-5 (Ubuntu):
status: Incomplete → Expired
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.