Am 13.07.2012 10:45, schrieb Kevin Wolf:
> Am 12.07.2012 19:07, schrieb Stefan Weil:
>> Great that you address this issue!
>> I have two annotations, please see below.
>>
>>
>> Am 12.07.2012 16:27, schrieb Kevin Wolf:
>>> valgrind tends to get confused and report false positives when you
>>> switch
Am 12.07.2012 19:07, schrieb Stefan Weil:
> Great that you address this issue!
> I have two annotations, please see below.
>
>
> Am 12.07.2012 16:27, schrieb Kevin Wolf:
>> valgrind tends to get confused and report false positives when you
>> switch stacks and don't tell it about it.
>>
>> Signed
Am 12.07.2012 19:14, schrieb Peter Maydell:
> On 12 July 2012 15:27, Kevin Wolf wrote:
>> valgrind tends to get confused and report false positives when you
>> switch stacks and don't tell it about it.
>
> Does the sigaltstack backend need anything similar?
Don't know, I never used valgrind with
On 12 July 2012 15:27, Kevin Wolf wrote:
> valgrind tends to get confused and report false positives when you
> switch stacks and don't tell it about it.
Does the sigaltstack backend need anything similar?
-- PMM
Great that you address this issue!
I have two annotations, please see below.
Am 12.07.2012 16:27, schrieb Kevin Wolf:
valgrind tends to get confused and report false positives when you
switch stacks and don't tell it about it.
Signed-off-by: Kevin Wolf
---
configure| 18 ++
valgrind tends to get confused and report false positives when you
switch stacks and don't tell it about it.
Signed-off-by: Kevin Wolf
---
configure| 18 ++
coroutine-ucontext.c | 21 +
2 files changed, 39 insertions(+), 0 deletions(-)
diff --
