[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140712040931.GD179@brightrain.aerifal.cx>
Date: Sat, 12 Jul 2014 00:09:31 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Cc: Alpine <alpine-devel@...ts.alpinelinux.org>
Subject: Re: Solved: Re: [alpine-devel] Attempting to debug C++
library and command via valgrind
On Fri, Jul 11, 2014 at 09:03:40PM -0700, Isaac Dunham wrote:
> Hello,
> Just so everyone knows, someone on the sword-devel list (the person who
> asked me for valgrind output) found and fixed the bug.
> Rich, thanks for mentioning strace; that ended up being the key.
What did it end up being? Partly just curious, but I also figure it
might be useful to know if this was some sort of UB from the
application that corrupted stdio state (in which case it's a symptom
we might see again) or whether it was just an application logic bug
(writing the same thing twice).
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
