From owner-freebsd-current Wed Oct 31 12:48:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from owa-sj-1.digisle.com (owa-sj-1.digisle.com [167.216.153.124]) by hub.freebsd.org (Postfix) with ESMTP id 67D7037B407 for ; Wed, 31 Oct 2001 12:48:18 -0800 (PST) Received: from VWALL-SJ-1.digisle.com ([167.216.153.118]) by owa-sj-1.digisle.com with Microsoft SMTPSVC(5.0.2195.2966); Wed, 31 Oct 2001 12:49:46 -0800 Received: from 206.220.227.145 by VWALL-SJ-1.digisle.com (InterScan E-Mail VirusWall NT); Wed, 31 Oct 2001 15:48:09 -0500 Message-ID: <3BE06391.A83EBE@digisle.net> Date: Wed, 31 Oct 2001 12:48:17 -0800 From: Maksim Yevmenkin Organization: Digital Island X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: [Fwd: weird -current gdb/gcc(?) problem] Content-Type: multipart/mixed; boundary="------------83E90AF974490B05C9D2DD9D" X-OriginalArrivalTime: 31 Oct 2001 20:49:46.0224 (UTC) FILETIME=[930DBF00:01C1624D] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------83E90AF974490B05C9D2DD9D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------83E90AF974490B05C9D2DD9D Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <3BE05A00.3EE3DDAD@digisle.net> Date: Wed, 31 Oct 2001 12:07:28 -0800 From: Maksim Yevmenkin Organization: Digital Island X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "Alexander N. Kabaev" Subject: Re: weird -current gdb/gcc(?) problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Alexander N. Kabaev" wrote: > > What is the problem exactly? It is hard to guess that from the > information you posted. > > > foo (i=1, s=10244, c=-54 'J', str=0x804855b "test") at prog1.c:13 > Is that what bothers you? It happens because > your code is compiled with no optimization, and that causes gcc to > allocate temporary backing storage for all parameters in the function > foo. When you type an 's' command to step into the foo function from > main, gcc stops immediately after function stack frame has been > initialized but before parameters have been copied into their respective > temporary locations. yes, but i posted wrong output :( try to do the same but use "-ggdb" instead of "-g" switch. even if you step info function some funny things happen. you can try to do both "-O2 -ggdb" vs. "-ggdb" only. thanks, max --------------83E90AF974490B05C9D2DD9D-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message