From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 21 22:39:34 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59905106566B for ; Fri, 21 Oct 2011 22:39:34 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 055508FC15 for ; Fri, 21 Oct 2011 22:39:33 +0000 (UTC) Received: by qyg14 with SMTP id 14so5164710qyg.13 for ; Fri, 21 Oct 2011 15:39:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; bh=ANBF92++NfU0ruhc3b1mkU//u/VCuNTrvy0bnMwf0TA=; b=ho5wYSnQGLF/EQjnuYUs5r3i9vXDJmP29FnKBmOrJtHVsyNOPxtXeTaSMjYBYxQyiz TLrag7O4zrDBrK6EL1Wz1AyGNT4KgoKROTJ3GK2F3mBCP9vRbviPLWjNDfCPYFXWSbqe mNJl7KQ0thzeKREiHOBJdRbiVxr6BOewg8R74= Received: by 10.229.44.206 with SMTP id b14mr3470356qcf.175.1319236773381; Fri, 21 Oct 2011 15:39:33 -0700 (PDT) Received: from kan.dnsalias.net (c-24-63-226-98.hsd1.ma.comcast.net. [24.63.226.98]) by mx.google.com with ESMTPS id hf9sm16702834qab.16.2011.10.21.15.39.31 (version=SSLv3 cipher=OTHER); Fri, 21 Oct 2011 15:39:32 -0700 (PDT) Date: Fri, 21 Oct 2011 18:39:24 -0400 From: Alexander Kabaev To: Garrett Cooper Message-ID: <20111021183924.2158d226@kan.dnsalias.net> In-Reply-To: References: <20111020082234.GA4568@britannica.bec.de> <4EA00DEF.3030905@FreeBSD.org> <20111020190553.6bf95790@kan.dnsalias.net> <20111020192653.6425f018@kan.dnsalias.net> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/28q.UctdIFDz6cjc75RVw0."; protocol="application/pgp-signature" Cc: Wojciech Puchar , freebsd-hackers Subject: Re: .eh_frame, .eh_frame_hdr - how to remove that trash X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2011 22:39:34 -0000 --Sig_/28q.UctdIFDz6cjc75RVw0. Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 21 Oct 2011 00:54:32 -0700 Garrett Cooper wrote: > On Fri, Oct 21, 2011 at 12:51 AM, Wojciech Puchar > wrote: > >> on entry into each function, which is different from usual x86 > >> convention. > >> Asynchronous unwind info (yeah, same stuff you keep referring to as > >> crap), is the only way you can debug your program or get anything > >> remotely close to usable backtrace, by default. > > > > i understand but i DO NOT called compiler with -g option which > > clearly means that i do not want to debug isn't it? >=20 > It seems like a binutils bug (or somewhere in that immediate > neighborhood) because all debugging related sections should be > stripped out by strip including unwind, correct? > Thanks, > -Garrett NO. Unwind info is a part of the ABI, and its relationship to debug flags as well as to wishes of the OP is very remote. --=20 Alexander Kabaev --Sig_/28q.UctdIFDz6cjc75RVw0. Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iD8DBQFOofSiQ6z1jMm+XZYRArF8AJ9JiBYRo8W883pcxREti/Q9ftR/3ACgpiXs nNAWR+Lrpre2JkfGfTIgDSc= =+uf6 -----END PGP SIGNATURE----- --Sig_/28q.UctdIFDz6cjc75RVw0.--