X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from brightrain.aerifal.cx (216-12-86-13.cv.mvl.ntelos.net [216.12.86.13]) by mail.alpinelinux.org (Postfix) with ESMTP id 2EC58DC03F9 for ; Thu, 10 Jul 2014 04:47:30 +0000 (UTC) Received: from dalias by brightrain.aerifal.cx with local (Exim 3.15 #2) id 1X56GK-0001ni-00; Thu, 10 Jul 2014 04:47:16 +0000 Date: Thu, 10 Jul 2014 00:47:16 -0400 From: Rich Felker To: musl@lists.openwall.com Cc: Jeff Pohlmeyer , Isaac Dunham , Alpine Subject: Re: [musl] Re: [alpine-devel] Attempting to debug C++ library and command via valgrind Message-ID: <20140710044716.GT179@brightrain.aerifal.cx> References: <20140709043946.GA1787@newbook> <20140710041348.GA4689@newbook> X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140710041348.GA4689@newbook> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: Rich Felker On Wed, Jul 09, 2014 at 09:13:49PM -0700, Isaac Dunham wrote: > On Wed, Jul 09, 2014 at 10:30:11AM -0500, Jeff Pohlmeyer wrote: > > On Tue, Jul 8, 2014 at 11:39 PM, Isaac Dunham wrote: > > > > > I've been trying to get Sword 1.7.3 (crosswire.org/sword) running on Alpine. > > > valgrind was recommended, but I can't get valgrind to run the command properly. > > > But when I do this, diatheke errors out: > > > diatheke: cannot load -b: No such file or directory > > > > > > I think it's a problem with the way valgrind tries to run musl's program loader. > > > > Try adding "/lib/ld-musl-i386.so.1" to the command line, just before > > the prgram name, > > e.g. > > > > valgrind --leak-check=full --track-origins=yes \ > > --keep-stacktraces=alloc-and-free \ > > /lib/ld-musl-i386.so.1 \ > > diatheke -b KJV -k Ps117 > > Thanks, this works for me. > > Of course it really runs slow and spits out a ton of information; > the log is over 400 kb at 5464 lines. (I suppose sending it to these lists > might be inappropriate, given the size...) If you have a reasonable place to dump the file you could just send a link to the list. But I think you're getting ahead of things. What actual failure is the program exhibiting? (Crash? Incorrect or no output? Error messages?) Depending on what happens, a gdb backtrace or an strace log may be more useful than the valgrind output. Rich --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---