X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=uTb2Vl2lE79GvwNbZgLO5/qsS532quLecEPIb9TCcycQXpv3ns0kZ mIOaodf3oiMVmAh1fxE8Fd7tlXhAwFwsYhWmZH7AOuXRbKf2kC8wtEveUPaMlqau UzqW/wjO5xDcCoJryH5h5DzBGH6HFqr5cMR6eVUXIGfBtUkUfGOgvQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=+RX9ZAzS7pePx33+610vfEpr4bc=; b=O3dGvvl1NHJlJ88hLcsivyH0LaAw zruzgq9crQHI0E3I5awzau8MemDtftB/QBqp/ekpYab5neeJ+1mAgV9K7Z4YOjy+ n/HW5y+F8oYXs69MjNMdWWQ3Od0Gk+FPB72oNsrOMJ1PEU/Llb+eRwjSOjrexeAD Olt2pVDWTQoxL+I= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_20,RDNS_NONE autolearn=no version=3.3.1 Date: Mon, 29 Jul 2013 13:06:26 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 64-bit gdb: invalid decimal " 0x22DBF0" Message-ID: <20130729110626.GB30069@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <51F33E9D DOT 9030703 AT cs DOT utoronto DOT ca> <51F3A133 DOT 8090805 AT star DOT sr DOT bham DOT ac DOT uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51F3A133.8090805@star.sr.bham.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) On Jul 27 11:30, Daniel Brown wrote: > I have also ran into this problem, in my case though I have managed > to reduce the issue down to an fgets call when reading a pipe. > The following code causes the issue for me if I try and debug it: > > #include > #include > > int main(int argc, char** argv) { > char out[100] = {0}; > FILE *pipe; > > if ((pipe = popen("uname -r", "rt")) == NULL) > fprintf(stderr,"Failed to execute popen command"); > > if(fgets(out, 100, pipe) == NULL) > fprintf(stderr,"Failed to read popen buffer"); > > printf("%s\n", out); > > pclose(pipe); > > return (EXIT_SUCCESS); > } > > I compile with `gcc -g main.c` then `gdb a.exe` and type `run`, the > error `invalid decimal " 0x23DBF0"` then pops up. > I have tried the latest snapshot cygwin1.dll (1.7.23s(0.268/5/3)) > and the error is still there. This is a problem in GDB, not in the Cygwin DLL. My mistake. I fetched the official 7.6 version of GDB since it already contained Cygwin x86_64 support so I thought it's sufficient. Unfortunately it doesn't handle special Cygwin strings in terms of Cygwin signal handling correctly. I'm just uploading a gdb-7.6.50 version build from current CVS which should fix this. Thanks for the reports, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple