[odb-users] Internal Compiler error

Alain-Serge Nagni asnagni at yahoo.com
Thu Oct 18 17:50:22 EDT 2018

Hi Boris,
	Problem fixed. It was an #include of a file that was causing the problem. I put the include  in a #ifdef #endif statement and the problem is gone.  What is strange is that it was not doing that with version 2.4.0 . Anyway thank you for your quick response and assistance .

Thank you,

> On Oct 18, 2018, at 7:34 AM, Boris Kolpackov <boris at codesynthesis.com> wrote:
> Alain-Serge Nagni <asnagni at yahoo.com> writes:
>> I'm not sure where to report this error. I'm trying to build my project
>> with the odb version 2.5.09 and I'm haveing an internal compiler error.
>>        *** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins.
>>        Event                            | Plugins
>>        PLUGIN_START_UNIT                | odb
>>        PLUGIN_PRAGMAS                   | odb
>>        PLUGIN_OVERRIDE_GATE             | odb
>>        during GIMPLE pass: *warn_unused_result
>>        In file included from /usr/local/include/odb/container-traits.hxx:217,
>>                         from <standard-odb-epilogue>:4:
>>        /usr/local/include/odb/std-unordered-set-traits.hxx: In function ‘void __static_initialization_and_destruction_0(int, int)’:
>>        /usr/local/include/odb/std-unordered-set-traits.hxx:122:1: internal compiler error: Segmentation fault
>>         }
>> Compiler:  gcc 8.1.1Os:  Linuxdistribution:  Fedora 28
> It would be helpful to get the stack trace as well as the test case
> (i.e., a subset of the header you are compiling) that reproduces the
> problem.
> To get the stack trace, re-run the ODB command with '-x -dH', for
> example:
> $ odb -x -dH ... test.hxx
> This should produce the core file. To analyze it, run:
> $ gdb -ex backtrace "$(g++ -print-file-name=cc1plus)" core
> This should produce the stack trace. Please include it with the
> test case.

More information about the odb-users mailing list