From: achkan <ashsalehi4133@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: segfault when functions are defined in headers or inlined
Date: Fri, 10 Jul 2015 11:04:00 -0000 [thread overview]
Message-ID: <1436526269636-1167315.post@n5.nabble.com> (raw)
In-Reply-To: <CAH6eHdTZY7Wh-TQDUNod50A-tJQecoxOMN=65jOjA91=JZjdWQ@mail.gmail.com>
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...). Anyhow, I am not asking you to debug our code, but whether or not
anyone has ever encountered this problem: "code that segfaults for every
inline
function, and no segfault when the definition is put in the .cpp files
instead of the headers." . If, no, then well... too bad for me :) thanks
again.
--
View this message in context: http://gcc.1065356.n5.nabble.com/segfault-when-functions-are-defined-in-headers-or-inlined-tp1167297p1167315.html
Sent from the gcc - Help mailing list archive at Nabble.com.
next prev parent reply other threads:[~2015-07-10 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 9:50 achkan
2015-07-10 10:33 ` Jonathan Wakely
2015-07-10 11:04 ` achkan [this message]
2015-07-10 11:10 ` Jonathan Wakely
2015-07-10 11:21 ` achkan
2015-07-10 14:32 ` Ángel González
2015-07-10 15:32 ` achkan
2015-07-10 14:28 johnsfine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1436526269636-1167315.post@n5.nabble.com \
--to=ashsalehi4133@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).