From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4666 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Re: Last call for bugfixes for 1.0 Date: Sun, 16 Mar 2014 15:06:08 -0400 Message-ID: <20140316190608.GI26358@brightrain.aerifal.cx> References: <20140315075223.GA27718@brightrain.aerifal.cx> <5325BE5E.6020001@rwth-aachen.de> <20140316152533.GG26358@brightrain.aerifal.cx> <5325ED35.3020106@rwth-aachen.de> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1394996778 5544 80.91.229.3 (16 Mar 2014 19:06:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 16 Mar 2014 19:06:18 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4670-gllmg-musl=m.gmane.org@lists.openwall.com Sun Mar 16 20:06:24 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1WPGO8-0000ZV-0N for gllmg-musl@plane.gmane.org; Sun, 16 Mar 2014 20:06:24 +0100 Original-Received: (qmail 9441 invoked by uid 550); 16 Mar 2014 19:06:23 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 9433 invoked from network); 16 Mar 2014 19:06:22 -0000 Content-Disposition: inline In-Reply-To: <5325ED35.3020106@rwth-aachen.de> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:4666 Archived-At: On Sun, Mar 16, 2014 at 07:28:05PM +0100, Thomas Kreuzer wrote: > On 16.03.2014 16:25, Rich Felker wrote: > >Have you done analysis to determine that this has anything to do with > >musl's fgetln function? Short of that, I suspect it's just an ordinary > >crash in your fgetln. There's no reason they should be interfering; > >for static linking, if fgetln is already defined then musl's fgetln.o > >won't even get linked, and for dynamic linking, your symbol overrides > >and nothing else accesses musl's fgetln symbol > > As I said, if I just rename the function it works perfectly. But it > doesn't seem to be a problem of musl either. > Sorry for making the wrong call, the problem must be somewhere else > in my tool chain If you can make a self-contained example to reproduce the problem, I can take a look at it. Otherwise I don't know what I can do to help though, and my guess is still that it's not specifically caused my musl. Rich