From: Florian Weimer <fweimer@redhat.com>
To: Maxim Blinov <maxim.blinov@embecosm.com>
Cc: gdb@sourceware.org
Subject: Re: use of %fs segment register in x86_64 with -fstack-check
Date: Wed, 04 Mar 2020 09:36:00 -0000 [thread overview]
Message-ID: <87zhcw8nvt.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CADmoyEiiCOqjvkydY+OQUN+hVBKidLXDc7A4o+fZgRj3meUAYw@mail.gmail.com> (Maxim Blinov's message of "Tue, 3 Mar 2020 14:52:45 +0000")
* Maxim Blinov:
> I'm looking at some -fstack-check'ed code, and would appreciate it if
> some gdb x86_64 gurus could double check my understanding of a trivial
> example
What's your motivation for this? -fstack-check is mostly there to
support certain Ada uses, yet you post a C snippet.
The more generally useful stack overflow detection switch is called
-fstack-clash-protection.
Thanks,
Florian
prev parent reply other threads:[~2020-03-04 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 14:53 Maxim Blinov
2020-03-03 16:51 ` Ruslan Kabatsayev
[not found] ` <CADmoyEgaCKp3nNg1Yw_8R2QDhEpd3cuaTSFDNFzSiesqerwrWQ@mail.gmail.com>
2020-03-03 18:43 ` Fwd: " Maxim Blinov
2020-03-03 20:03 ` Ruslan Kabatsayev
2020-03-04 9:36 ` Florian Weimer [this message]
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=87zhcw8nvt.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gdb@sourceware.org \
--cc=maxim.blinov@embecosm.com \
/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