Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

9.8K
active users

hachyderm.io: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.5

#memorysafety

4 posts3 participants0 posts today
Continued thread
Public
Anisse

"Unsafe is the stupidest language feature (on a technical level)", Nadri says. It's just an arbitrary constraint to call code with the unsafe keyword, with only the unsafe keyword. Therefore, it's mostly a social that "works super well".

Nadri in front of unsafe-related slides.
#RustLang#Unsafe#MemorySafety
Public
Chaz Haws

I have a question about #memorysafety in #zig.

What are the risks in this code?

// using Zig's ReleaseSafe mode
const mem = try std.fmt.allocPrint(std.heap.page_allocator, "Hello {s}", .{"World"});
std.debug.print("text is {s}\n", .{mem});
std.heap.page_allocator.free(mem);
std.debug.print("text is {s}\n", .{mem}); // a programming error occurred here

Public *
T_X

#RemiPommarel found and fixed a bug/regression in a recent change someone had added to @batadv in the #Linux #kernel. One take home message from Remi:

"On a side note, I am all about #hardening and #MemorySafety stuff but if that means impacting readability and spending more time trying to please the tool than thinking about the #correctness of the code change, that's where we end up converting a perfectly fine #code into a logically flawed one."
(hash tags added by me)

patchwork.open-mesh.org/projec

patchwork.open-mesh.orgbatman-adv: Fix incorrect offset in batadv_tt_tvlv_ogm_handler_v1() - Patchwork
Public
The New Stack

Google just took a big step forward in C++ safety. By retrofitting spatial memory safety onto their C++ code, they've improved security across services like Gmail & YouTube with minimal performance impact. David Cassel dives in more in his article.

thenewstack.io/google-retrofit

The New Stack · Google 'Retrofits' Spatial Memory Safety Onto C++Google researchers showed they were able to "retrofit" spatial safety onto their C++ codebases, and to do it with a surprisingly low impact on performance.
Public
Marco Ivaldi

Story-time: C++, bounds checking, performance, and compilers

chandlerc.blog/posts/2024/11/s

See also: Retrofitting spatial safety to hundreds of millions of lines of C++

security.googleblog.com/2024/1

chandlerc.blog · Story-time: C++, bounds checking, performance, and compilersRecently, several of my colleagues at Google shared the story of how we are retrofitting spatial safety onto our monolithic C++ codebase: https://security.googleblog.com/2024/11/retrofitting-spatial-safety-to-hundreds.html I wanted to have a bit of story-time about some of the strange ways that all this came to be, at least as I remember things. There are some really interesting developments that led us here, and some important lessons to learn from that history. Do note that this is just my retrospective memory. It’s entirely possible I’m misremembering some of it (let me know if so!). It’s also limited to my perspective, and others may have seen very different aspects of things (please share!).
#c#cpp#memorysafety
ExploreLive feeds
About