Date: Sat, 12 Jul 2014 00:09:31 -0400
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: Alpine <alpine-devel@lists.alpinelinux.org>
Subject: Re: [musl] Solved: Re: [musl][alpine-devel] Attempting to debug C++
 library and command via valgrind
Message-ID: <20140712040931.GD179@brightrain.aerifal.cx>
References: <20140709043946.GA1787@newbook>
 <CAEuRe+2zBM3L+Vhfiqgpnq0cm7ZF1=5ZTBo-F-iP9UsNTHG-1A@mail.gmail.com>
 <20140710041348.GA4689@newbook>
 <20140710044716.GT179@brightrain.aerifal.cx>
 <20140710065006.GB4777@newbook>
 <20140711033933.GW179@brightrain.aerifal.cx>
 <20140712040339.GB1789@newbook>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140712040339.GB1789@newbook>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: Rich Felker <dalias@aerifal.cx>

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


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---