From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/1220 Path: news.gmane.org!not-for-mail From: Tom Tromey Newsgroups: gmane.linux.lib.musl.general,gmane.comp.lib.gnulib.bugs Subject: Re: musl, printf out-of-memory test Date: Thu, 21 Jun 2012 13:58:30 -0600 Message-ID: <87lijgl9nd.fsf@fleche.redhat.com> References: <20120609230541.47eac2de@newbook> <4210755.aMrNX6YhFs@linuix> <20120620015249.GT163@brightrain.aerifal.cx> <2880353.4bDTyI3WGR@linuix> <87lijiw8mp.fsf@rho.meyering.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1340311372 17449 80.91.229.3 (21 Jun 2012 20:42:52 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 21 Jun 2012 20:42:52 +0000 (UTC) Cc: Bruno Haible , Rich Felker , bug-gnulib@gnu.org To: musl@lists.openwall.com Original-X-From: musl-return-1221-gllmg-musl=m.gmane.org@lists.openwall.com Thu Jun 21 22:42:50 2012 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 1ShoDK-0003Jo-1e for gllmg-musl@plane.gmane.org; Thu, 21 Jun 2012 22:42:50 +0200 Original-Received: (qmail 32194 invoked by uid 550); 21 Jun 2012 20:42:49 -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 18217 invoked from network); 21 Jun 2012 19:58:50 -0000 X-Attribution: Tom In-Reply-To: <87lijiw8mp.fsf@rho.meyering.net> (Jim Meyering's message of "Wed, 20 Jun 2012 13:00:30 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 Xref: news.gmane.org gmane.linux.lib.musl.general:1220 gmane.comp.lib.gnulib.bugs:31121 Archived-At: >>>>> "Jim" == Jim Meyering writes: Jim> That is correct. It is a feature of gdb-7.0 and newer. Jim> You can inspect (watch/break-at/etc.) the same address and expect it Jim> to refer to the same memory location in multiple invocations. Jim> This makes gdb's command-line history even more useful. gdb defaults to this for development convenience. You can change it though, see "set disable-randomization". Tom