[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: Runtime checking of port handling
From: |
Samuel Thibault |
Subject: |
Re: RFC: Runtime checking of port handling |
Date: |
Sat, 4 Jun 2016 17:32:06 +0200 |
User-agent: |
Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) |
Hello,
Justus Winter, on Sat 04 Jun 2016 15:45:15 +0200, wrote:
> tl;dr: Compiler-assisted runtime checking of port handling in
> variables with automatic storage duration. Do we want to go there?
That's interesting, but the proposed way would need annotating the whole
source code, I'm afraid we'll make mistakes there. Passing a port to a
function that will deallocate it will probably need another macro BTW.
Ideally we'd have a static analysis tool which knows about the mig rules
for port references. Perhaps LeakSanitizer could be taught that? (we
probably want to port it to Hurd, anyway, and it seems very portable)
Samuel
- RFC: Runtime checking of port handling, Justus Winter, 2016/06/04
- [PATCH hurd 1/2] xxx print fail, Justus Winter, 2016/06/04
- [PATCH hurd 2/2] libshouldbeinlibc: add safe port handling macros, Justus Winter, 2016/06/04
- Re: [PATCH hurd 2/2] libshouldbeinlibc: add safe port handling macros, Ludovic Courtès, 2016/06/05
- Re: [PATCH hurd 2/2] libshouldbeinlibc: add safe port handling macros, Samuel Thibault, 2016/06/05
- Re: [PATCH hurd 2/2] libshouldbeinlibc: add safe port handling macros, Ludovic Courtès, 2016/06/06
- Re: [PATCH hurd 2/2] libshouldbeinlibc: add safe port handling macros, Thomas Schwinge, 2016/06/06
- Re: [PATCH hurd 2/2] libshouldbeinlibc: add safe port handling macros, Samuel Thibault, 2016/06/06
- Re: [PATCH hurd 2/2] libshouldbeinlibc: add safe port handling macros, Ludovic Courtès, 2016/06/06
Re: [PATCH hurd 1/2] xxx print fail, Samuel Thibault, 2016/06/04
Re: RFC: Runtime checking of port handling,
Samuel Thibault <=