Adam Shostack  2d ago

Is this a reasonable definition of memory safety?

"Memory safety is a property, where all memory access is mediated by the platform to ensure that program memory can only be changed using the appropriate library functions."

(I feel ones at https://www.memorysafety.org/docs/memory-safety/ and https://en.wikipedia.org/wiki/Memory_safety start out too abstractly)

#security #cheri #memoryManagement

What is memory safety and why does it matter?

Memory safety is a property of some programming languages that prevents programmers from introducing certain types of bugs related to how memory is used. Since memory safety bugs are often security issues, memory safe languages are more secure than languages that are not memory safe. Memory safe languages include Rust, Go, C#, Java, Swift, Python, and JavaScript. Languages that are not memory safe include C, C++, and assembly. Types of Memory Safety Bugs To begin understanding memory safety bugs, we'll consider the example of an application that maintains to do lists for many users. We'll look at a couple of the most common types of memory safety errors that can occur in programs that are not memory safe.

Prossimo
Snapp iOS Weekly6d ago

Ever wondered what happened to "zombie objects" in Swift's memory management? Side tables now decouple object lifetime from weak reference bookkeeping, enabling more efficient ARC. A deep dive into strong, weak, and unowned reference trade-offs.

πŸ”—: https://livsycode.com/swift/swift-arc-from-zombie-objects-to-side-tables/ by Artem Mirzabekian

#Swift #MemoryManagement #iOSDev

Swift ARC: From Zombie Objects to Side Tables β†’ Livsy Code

Greetings, traveler! Reference counting is one of those topics every iOS developer learns early and then rarely revisits in depth. At the surface, it feels predictable: objects are retained, released, and eventually deallocated. Underneath, the implementation is far more nuanced. The way Swift manages memory has changed since its early versions, and those changes reflect

Livsy Code β†’ Learn Swift the smart way
LobstersMay 17

Manual Memory Management

https://dayvster.com/blog/manual-memory-management/

#Programming #MemoryManagement #SoftwareEngineering

Manual Memory Management

It's not as scary as it sounds

sayzardMay 16

Experience Layer for AI

CortexDB V1λŠ” AI μ—μ΄μ „νŠΈμ˜ κ²½ν—˜ λ ˆμ΄μ–΄λ₯Ό κ΅¬μΆ•ν•˜λŠ” λ°μ΄ν„°λ² μ΄μŠ€λ‘œ, κΈ°μ‘΄ LLMκ³Ό 지식 λ ˆμ΄μ–΄λ₯Ό λ„˜μ–΄ μ‚¬μš©μžκ°€ κ²ͺ은 사건과 신념을 μ²΄κ³„μ μœΌλ‘œ κ΄€λ¦¬ν•œλ‹€. λ‹€μ„― 개의 λ©”λͺ¨λ¦¬ 계측(이벀트, μ—ν”Όμ†Œλ“œ, 사싀, 신념, 이해)을 톡해 AIκ°€ μ™œ κ·Έλ ‡κ²Œ νŒλ‹¨ν–ˆλŠ”μ§€ κ·Όκ±°λ₯Ό 좔적할 수 있으며, LongMemEval-S와 LoCoMo λ²€μΉ˜λ§ˆν¬μ—μ„œ μ΅œμ²¨λ‹¨ μ„±λŠ₯을 κΈ°λ‘ν–ˆλ‹€. 8μ£Ό λ§Œμ— 개발된 이 μ‹œμŠ€ν…œμ€ PASETO 인증, 계측적 λ„€μž„μŠ€νŽ˜μ΄μŠ€, GDPR μ€€μˆ˜ μ‚­μ œ κΈ°λŠ₯ λ“± 싀무 μ μš©μ— ν•„μš”ν•œ κΈ°λŠ₯도 ν¬ν•¨ν•œλ‹€. ν–₯ν›„ V2μ—μ„œλŠ” κ²½ν—˜μ„ μ’…ν•©ν•˜λŠ” 톡합 단계가 μΆ”κ°€λ˜μ–΄ λ”μš± 지λŠ₯적인 λ©”λͺ¨λ¦¬ κΈ°λŠ₯을 μ œκ³΅ν•  μ˜ˆμ •μ΄λ‹€.

https://cortexdb.ai/blog/v1

#aiaagents #memorymanagement #cortexdb #llm #distributedinfrastructure

CortexDB V1: The Experience Layer for AI Agents

93.8% on LongMemEval-S. 86.9% on LoCoMo. Five memory layers. Hierarchical scopes. PASETO auth. The third layer every AI agent has been missing β€” shipped.

N-gated Hacker NewsMay 14
Ah, yet another #GitHub project promising to revolutionize the world by... generating LLVM IR without malloc. πŸš€ Because who needs memory management anyway? πŸ˜‚ It's like building a spaceship out of cardboard and claiming you've solved interstellar travel. 🌌
https://github.com/glouw/nibble #LLVMIR #memorymanagement #codinghumor #softwaredevelopment #techinnovation #HackerNews #ngated
GitHub - glouw/nibble: Generating LLVM IR without malloc or external dependencies

Generating LLVM IR without malloc or external dependencies - glouw/nibble

GitHub
sayzardMay 11

Can I use agents – features across coding agents

이 λ¬Έμ„œλŠ” μ½”λ”© μ—μ΄μ „νŠΈ κ°œλ°œμžλ“€μ„ μœ„ν•œ μ—μ΄μ „νŠΈ κΈ°λŠ₯κ³Ό ν™•μž₯성에 λŒ€ν•΄ μƒμ„Ένžˆ μ„€λͺ…ν•©λ‹ˆλ‹€. μ—μ΄μ „νŠΈμ˜ 라이프사이클 ν›…, λͺ…λ Ήμ–΄ 및 파일 μ ‘κ·Ό μ œμ–΄, ν”„λ‘¬ν”„νŠΈ 검증, MCP(Model Context Protocol) 지원, λ©”λͺ¨λ¦¬ 관리, λ‚΄μž₯ 도ꡬ λ“± λ‹€μ–‘ν•œ κΈ°λŠ₯을 μ²΄κ³„μ μœΌλ‘œ μ •λ¦¬ν•˜μ—¬, κ°œλ°œμžκ°€ μ—μ΄μ „νŠΈλ₯Ό μ„ νƒν•˜κ±°λ‚˜ μ›Œν¬ν”Œλ‘œμš°λ₯Ό ꡬ좕할 λ•Œ μ°Έκ³ ν•  수 μžˆλ„λ‘ κ΅¬μ„±λ˜μ–΄ μžˆμŠ΅λ‹ˆλ‹€. 특히 μ„Έμ…˜ 관리, 도ꡬ μ‹€ν–‰ μ „ν›„ ν›…, 닀쀑 μ—μ΄μ „νŠΈ ν˜Έν™˜μ„±, OAuth 인증, μ»¨ν…μŠ€νŠΈ μ••μΆ• λ“± 싀무에 μœ μš©ν•œ κΈ°λŠ₯듀을 ν¬ν•¨ν•˜κ³  μžˆμŠ΅λ‹ˆλ‹€. μ΄λŠ” μ½”λ”© μ—μ΄μ „νŠΈ 개발 및 μš΄μ˜μ— 직접 적용 κ°€λŠ₯ν•œ μ’…ν•© κ°€μ΄λ“œ 역할을 ν•©λ‹ˆλ‹€.

https://caniuseagents.com/

#codingagents #agentframework #mcp #hooks #memorymanagement

Can I Use Agents?

Compatibility tables for AI coding agent features. Compare support across Claude Code, Cline, Codex CLI, Copilot, Cursor, and Windsurf.

sayzardMay 8

(Un)portable defer in C

C μ–Έμ–΄μ—μ„œ μžμ› ν•΄μ œλ₯Ό μžλ™ν™”ν•˜λŠ” defer κΈ°λŠ₯은 μ—¬λŸ¬ μ œμ•ˆκ³Ό κ΅¬ν˜„μ΄ μ‘΄μž¬ν•˜μ§€λ§Œ ν‘œμ€€μœΌλ‘œ μ±„νƒλ˜μ§€λŠ” μ•Šμ•˜λ‹€. GCC의 cleanup 속성과 nested function, Clang의 blocks, MSVC의 structured exception handling λ“± 각 μ»΄νŒŒμΌλŸ¬λ³„λ‘œ λ‹€λ₯Έ λ°©μ‹μœΌλ‘œ κ΅¬ν˜„ κ°€λŠ₯ν•˜λ‚˜, λ³΄μ•ˆ λ¬Έμ œλ‚˜ ν˜Έν™˜μ„± ν•œκ³„κ°€ μžˆλ‹€. κ°„λ‹¨ν•œ for λ£¨ν”„λ‚˜ μŠ€νƒ 기반 κ΅¬ν˜„λ„ μžˆμ§€λ§Œ μ‘°κΈ° μ’…λ£Œ μ‹œ λ™μž‘ 보μž₯이 μ–΄λ ΅κ±°λ‚˜ λ³„λ„μ˜ λ°˜ν™˜ 맀크둜 μ‚¬μš©μ΄ ν•„μš”ν•˜λ‹€. C23 ν‘œμ€€μ— deferκ°€ 포함될 κ°€λŠ₯성이 μžˆμœΌλ‚˜, ν˜„μž¬λŠ” μ»΄νŒŒμΌλŸ¬λ³„ νŠΈλ ˆμ΄λ“œμ˜€ν”„λ₯Ό κ³ λ €ν•΄ 선택해야 ν•œλ‹€.

https://antonz.org/defer-in-c/

#cprogramming #defer #gcc #clang #memorymanagement

(Un)portable defer in C

Eight ways to implement defer in C.

sayzardMay 6

Claude Managed Agents can engage in a "dreaming" process to preserve memories
Anthropic은 Claude Managed Agents에 'dreaming' κΈ°λŠ₯을 λ„μž…ν–ˆλ‹€. 이 κΈ°λŠ₯은 졜근 이벀트λ₯Ό κ²€ν† ν•˜μ—¬ μ€‘μš”ν•œ 정보λ₯Ό 기얡에 μ €μž₯ν•˜κ³ , μž₯κΈ° ν”„λ‘œμ νŠΈλ‚˜ 닀쀑 μ—μ΄μ „νŠΈ μž‘μ—…μ—μ„œ μ€‘μš”ν•œ νŒ¨ν„΄κ³Ό 정보λ₯Ό μœ μ§€ν•˜λŠ” 데 도움을 μ€€λ‹€. dreaming은 ν˜„μž¬ 연ꡬ 미리보기 단계이며, μžλ™ λ˜λŠ” μˆ˜λ™μœΌλ‘œ λ©”λͺ¨λ¦¬ 변경을 관리할 수 μžˆλ‹€. 이 κΈ°λŠ₯은 LLM의 μ œν•œλœ μ»¨ν…μŠ€νŠΈ μœˆλ„μš° 문제λ₯Ό λ³΄μ™„ν•˜λ©°, 닀쀑 μ—μ΄μ „νŠΈ ν˜‘μ—…μ— 특히 μœ μš©ν•˜λ‹€.

https://arstechnica.com/ai/2026/05/anthropics-claude-can-now-dream-sort-of/

#anthropic #claude #managedagents #dreaming #memorymanagement

Anthropic's Claude Managed Agents can now "dream," sort of

Also, 5-hour usage limits will double for Pro and Max users of Claude Code.

Ars Technica
Snapp iOS WeeklyMay 5

Your view disappeared but the view model's 𝑑𝑒𝑖𝑛𝑖𝑑 never fired? Modifiers like π‘œπ‘›π‘†π‘’π‘π‘šπ‘–π‘‘ and π‘ π‘’π‘Žπ‘Ÿπ‘β„Žπ‘Žπ‘π‘™π‘’ can hold onto memory longer than expected inside π‘π‘Žπ‘£π‘–π‘”π‘Žπ‘‘π‘–π‘œπ‘›π‘†π‘‘π‘Žπ‘π‘˜. Weak captures solve it.

πŸ”—: https://livsycode.com/swiftui/when-swiftui-modifiers-hold-onto-memory-longer-than-expected/ by Artem Mirzabekian

#SwiftUI #MemoryManagement #iOSDev

When SwiftUI modifiers hold onto memory longer than expected β†’ Livsy Code

Greetings, traveler! Every experienced iOS engineer eventually runs into the same unsettling moment: you navigate back from a screen, expect deinit to fire, and nothing happens. The view disappears but the memory does not. In SwiftUI projects, this behavior has repeatedly surfaced around three modifiers: onSubmit, searchable, and refreshable. The pattern looks similar each time.

Livsy Code β†’ Learn Swift the smart way
Snapp iOS WeeklyApr 30

Memory leaks don't crash your app immediately - they just make it slower over time. Strong reference cycles in closures, delegates, timers, and async tasks are the usual culprits. Know when to use weak and unowned references.

πŸ”—: https://hackernoon.com/memory-leaks-in-swift-the-silent-killer-of-ios-apps by Flaregun-dev (@hackernoon)

#Swift #iOSDev #MemoryManagement

Memory Leaks in Swift: The Silent Killer of iOS Apps | HackerNoon

Understand memory leaks in Swift and iOS apps, including ARC behavior, retain cycles, closures, async tasks, and practical strategies