> On 4 Jun 2016, at 15:04, James Clarke wrote:
>
>> On 3 Jun 2016, at 19:36, Samuel Thibault wrote:
>>
>> Samuel Thibault, on Fri 03 Jun 2016 20:35:13 +0200, wrote:
>>> Adam Richards, on Fri 03 Jun 2016 19:30:40 +0100, wrote:
On rebooting and reverting to gnumach-1.6-486.gz this is not an
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
That looks useful, yes, please commit :)
Justus Winter, on Sat 04 Jun 2016 15:47:51 +0200, wrote:
> ---
> libshouldbeinlibc/assert-backtrace.c | 8
> libshouldbeinlibc/assert-backtrace.h | 6 ++
> 2 files changed, 14 insertions(+)
>
> diff --git a/libshouldbeinlibc/assert-backtrace.
> On 3 Jun 2016, at 19:36, Samuel Thibault wrote:
>
> Samuel Thibault, on Fri 03 Jun 2016 20:35:13 +0200, wrote:
>> Adam Richards, on Fri 03 Jun 2016 19:30:40 +0100, wrote:
>>> On rebooting and reverting to gnumach-1.6-486.gz this is not an issue.
>>
>> It could be worth bisecting the issue on
* libshouldbeinlibc/Makefile (SRCS, installhdrs): Add new file.
* libshouldbeinlibc/machx.h: New file.
---
libshouldbeinlibc/Makefile | 2 ++
libshouldbeinlibc/machx.h | 73 ++
trans/crash.c | 29 +-
3 files changed, 89 ins
---
libshouldbeinlibc/assert-backtrace.c | 8
libshouldbeinlibc/assert-backtrace.h | 6 ++
2 files changed, 14 insertions(+)
diff --git a/libshouldbeinlibc/assert-backtrace.c
b/libshouldbeinlibc/assert-backtrace.c
index ca23c8d..72a49e9 100644
--- a/libshouldbeinlibc/assert-backtrac
Hello :)
tl;dr: Compiler-assisted runtime checking of port handling in
variables with automatic storage duration. Do we want to go there?
Long version:
I recently found a pretty bad resource leak in our crash server and
pondered how to find such issues proactively. The main idea is to 1/
clear
