From owner-freebsd-current@FreeBSD.ORG Mon Jun 23 15:22:58 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6FB7FE27; Mon, 23 Jun 2014 15:22:58 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A57B2391; Mon, 23 Jun 2014 15:22:57 +0000 (UTC) Received: from [192.168.2.2] (unknown [77.243.161.229]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 21E535C37; Mon, 23 Jun 2014 17:22:46 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_E75D72F2-3714-4ECF-B471-472695121C69"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: [CURRENT]: weird memory/linker problem? From: Dimitry Andric In-Reply-To: <20140623163115.03bdd675.ohartman@zedat.fu-berlin.de> Date: Mon, 23 Jun 2014 17:22:25 +0200 Message-Id: References: <20140622165639.17a1ba1e.ohartman@zedat.fu-berlin.de> <20140623163115.03bdd675.ohartman@zedat.fu-berlin.de> To: "O. Hartmann" X-Mailer: Apple Mail (2.1878.2) Cc: Adrian Chadd , FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 15:22:58 -0000 --Apple-Mail=_E75D72F2-3714-4ECF-B471-472695121C69 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 23 Jun 2014, at 16:31, O. Hartmann = wrote: > Am Sun, 22 Jun 2014 10:10:04 -0700 > Adrian Chadd schrieb: >> When they segfault, where do they segfault? ... > GIMP, LaTeX work, nothing special, but a bit memory consuming = regrading GIMP) I tried > updating the ports tree and surprisingly the tree is left over in a = unclean condition > while /usr/bin/svn segfault (on console: pid 18013 (svn), uid 0: = exited on signal 11 > (core dumped)). >=20 > Using /usr/local/bin/svn, which is from the devel/subversion port, = performs well, while > FreeBSD 11's svn contribution dies as described. It did not hours ago! I think what Adrian meant was: can you run svn (or another crashing program) in gdb, and post a backtrace? Or maybe run ktrace, and see where it dies? Alternatively, put a core dump and the executable (with debug info) in a tarball, and upload it somewhere, so somebody else can analyze it. -Dimitry --Apple-Mail=_E75D72F2-3714-4ECF-B471-472695121C69 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlOoRj8ACgkQsF6jCi4glqN/UACcDBvJGDicjQqEG5wwDNqfMab1 JdsAnj3lO06vtaL2eaLe2PH95Xw+0MkV =LZhO -----END PGP SIGNATURE----- --Apple-Mail=_E75D72F2-3714-4ECF-B471-472695121C69--