This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: segfault when functions are defined in headers or inlined
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: achkan <ashsalehi4133 at gmail dot com>
- Cc: gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Fri, 10 Jul 2015 12:10:15 +0100
- Subject: Re: segfault when functions are defined in headers or inlined
- Authentication-results: sourceware.org; auth=none
- References: <1436521831306-1167297 dot post at n5 dot nabble dot com> <CAH6eHdTZY7Wh-TQDUNod50A-tJQecoxOMN=65jOjA91=JZjdWQ at mail dot gmail dot com> <1436526269636-1167315 dot post at n5 dot nabble dot com>
On 10 July 2015 at 12:04, achkan wrote:
> Thanks a lot for you answer. Yes, this happens with every inline function. If
> I could write a simple, self-contained complete program that shows the
> problem, I would gladly do it (I think this would take me more than a
> year...).
That's ridiculous. If it happens with *every* function then you could
write a single file with one inline function and call it from main(),
if that fails you've reproduced the problem (in a lot less than a
year!) and if it doesn't fail then it proves it doesn't happen for
*every* function and there must be something particular to your
library. Maybe http://stackoverflow.com/help/mcve will help.