From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95026] Alien Isolation segfault after initial loading screen/video
Date: Wed, 20 Apr 2016 07:27:15 +0000 [thread overview]
Message-ID: <bug-95026-502-RYDTt9c6xX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95026-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 585 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95026
--- Comment #12 from Christoph Haag <haagch@frickel.club> ---
Yes, you are right. With CFLAGS and CXXFLAGS="-O2 -fno-inline-small-functions"
it does not crash.
Seems like the answers on stackoverflow apply here too and it's the inlined
functions that use up all the available stack memory. I don't know how that
works exactly but I guess all the local variables from the inlined functions
get added to the functions where they are inlined into, every time?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1383 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-20 7:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 20:15 [Bug 95026] Alien Isolation segfault after initial loading screen/video bugzilla-daemon
2016-04-19 20:52 ` bugzilla-daemon
2016-04-19 21:00 ` bugzilla-daemon
2016-04-19 21:27 ` bugzilla-daemon
2016-04-19 21:37 ` bugzilla-daemon
2016-04-19 22:02 ` bugzilla-daemon
2016-04-19 22:31 ` bugzilla-daemon
2016-04-19 22:34 ` bugzilla-daemon
2016-04-19 22:52 ` bugzilla-daemon
2016-04-19 23:00 ` bugzilla-daemon
2016-04-19 23:01 ` bugzilla-daemon
2016-04-20 3:29 ` bugzilla-daemon
2016-04-20 7:27 ` bugzilla-daemon [this message]
2016-04-25 23:40 ` bugzilla-daemon
2016-04-26 10:07 ` bugzilla-daemon
2016-04-29 16:54 ` bugzilla-daemon
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=bug-95026-502-RYDTt9c6xX@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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