From: Bernhard Krug <b.krug@elektronenpumpe.de>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>, newlib@sourceware.org
Subject: Re: [PATCH] libc: arm: setjmp jmp_buf exagerated size
Date: Wed, 15 Feb 2023 18:14:25 +0100 [thread overview]
Message-ID: <90ED6369-550C-40BA-ACCF-E90F7787258B@elektronenpumpe.de> (raw)
In-Reply-To: <d322cf3b-d615-3fcb-272c-f3146e1ab158@foss.arm.com>
On February 15, 2023 6:01:05 PM GMT+01:00, Richard Earnshaw <Richard.Earnshaw@foss.arm.com> wrote:
>
>But you can build your source file with a jmp_buf in it, and if you then end up linking it against a version of the library that expects a larger buffer it will end up corrupting data.
>
You are right. I didn't consider this in my MCU project yet :D
Thank you.
prev parent reply other threads:[~2023-02-15 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 22:47 Bernhard Krug
2023-02-15 11:09 ` [PATCH] " Bernhard Krug
2023-02-15 15:56 ` Bernhard Krug
2023-02-15 16:05 ` Bernhard Krug
2023-02-15 16:12 ` Richard Earnshaw
2023-02-15 16:40 ` Bernhard Krug
2023-02-15 17:01 ` Richard Earnshaw
2023-02-15 17:14 ` Bernhard Krug [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=90ED6369-550C-40BA-ACCF-E90F7787258B@elektronenpumpe.de \
--to=b.krug@elektronenpumpe.de \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=newlib@sourceware.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).