On Thu, Nov 21, 2019 at 09:44:56AM -0500, Rick Kern wrote:
> On Wed, Nov 20, 2019 at 11:29 AM Hendrik Leppkes
> wrote:
>
> > On Wed, Nov 20, 2019 at 5:00 PM Timo Rothenpieler
> > wrote:
> > >
> > > On 20.11.2019 13:51, Rick Kern wrote:
> > > > The current version of clang enables stack checking
On Wed, Nov 20, 2019 at 11:29 AM Hendrik Leppkes
wrote:
> On Wed, Nov 20, 2019 at 5:00 PM Timo Rothenpieler
> wrote:
> >
> > On 20.11.2019 13:51, Rick Kern wrote:
> > > The current version of clang enables stack checking by default, causing
> > > a crash when binaries are run.
> >
> > Why does
On Wed, Nov 20, 2019 at 5:00 PM Timo Rothenpieler wrote:
>
> On 20.11.2019 13:51, Rick Kern wrote:
> > The current version of clang enables stack checking by default, causing
> > a crash when binaries are run.
>
> Why does it trigger a crash? Doesn't it indicate something is wrong that
> should
On 20.11.2019 13:51, Rick Kern wrote:
The current version of clang enables stack checking by default, causing
a crash when binaries are run.
Why does it trigger a crash? Doesn't it indicate something is wrong that
should be fixed instead?
___
The current version of clang enables stack checking by default, causing
a crash when binaries are run.
Fixes #8073 using the -fno-stack-check work-around mentioned in the ticket.
---
configure | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure b/configure
index 8f4f2884cf..97e614f18a
