Displaying 4 results from an estimated 4 matches for "allocate_stack".
2015 Oct 02
2
buildbot failure in LLVM on clang-cmake-mips
Thanks. From the debugging I've done so far it looks like it could be another 32-bit big-endian specific bug. It seems to be segfaulting in the memset() in allocate_stack.c (from glib) because given stack pointer is null. I'm guessing this is because it read the wrong half of a 64-bit value somewhere but I haven't identified where it goes wrong.
________________________________________
From: Evgenii Stepanov [eugeni.stepanov at gmail.com]
Sent: 02 October 20...
2018 Dec 02
0
[PATCH nbdkit 2/4] valgrind: Add --show-leak-kinds=all and comprehensive list of suppressions.
...rind-suppressions
+++ b/valgrind/nbdkit.suppressions
@@ -1,5 +1,5 @@
# nbdkit valgrind suppressions
-# Copyright (C) 2016 Red Hat Inc.
+# Copyright (C) 2016-2018 Red Hat Inc.
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
@@ -50,22 +50,13 @@
fun:allocate_stack
}
-# Allow thread-local storage from pthread_create to leak.
-{
- nbdkit_3
- Memcheck:Leak
- fun:calloc
- ...
- fun:_dl_allocate_tls
-}
-
# close methods are not guaranteed to be called if a connection is in
# progress when the server is being shut down, so leaks in various
# *_open func...
2015 Oct 02
3
buildbot failure in LLVM on clang-cmake-mips
I've just noticed that this is a new test added in r248325 and has never passed on this builder. Added the author of the test (Evgeniy).
From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Daniel Sanders via llvm-dev
Sent: 01 October 2015 20:34
To: David Blaikie
Cc: llvm-dev
Subject: Re: [llvm-dev] buildbot failure in LLVM on clang-cmake-mips
> > I do. I'll take
2018 Dec 02
10
[PATCH nbdkit 0/4] Multiple valgrind improvements and possible security fix.
I worked out why valgrind wasn't being applied to nbdkit when run by
many of the tests (patches 1-2). Unfortunately I'm not able to make
it actually fail tests when valgrind fails. Although the situation is
marginally improved in that you can now manually examine the *.log
files and find valgrind failures that way. Also adds valgrinding of
the Python plugin (patch 3).
Along the way I