From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29471 invoked by alias); 27 Dec 2010 22:34:00 -0000 Received: (qmail 29461 invoked by uid 22791); 27 Dec 2010 22:34:00 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from e24smtp02.br.ibm.com (HELO e24smtp02.br.ibm.com) (32.104.18.86) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 27 Dec 2010 22:33:55 +0000 Received: from mailhub1.br.ibm.com (mailhub1.br.ibm.com [9.18.232.109]) by e24smtp02.br.ibm.com (8.14.4/8.13.1) with ESMTP id oBRMrE8q027463 for ; Mon, 27 Dec 2010 20:53:14 -0200 Received: from d24av04.br.ibm.com (d24av04.br.ibm.com [9.8.31.97]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id oBRMfFYJ1265668 for ; Mon, 27 Dec 2010 20:41:15 -0200 Received: from d24av04.br.ibm.com (loopback [127.0.0.1]) by d24av04.br.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id oBRMXp6K032734 for ; Mon, 27 Dec 2010 20:33:51 -0200 Received: from [9.78.144.32] ([9.78.144.32]) by d24av04.br.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id oBRMXpjM032728 for ; Mon, 27 Dec 2010 20:33:51 -0200 Message-ID: <4D19144E.1030504@linux.vnet.ibm.com> Date: Mon, 27 Dec 2010 22:34:00 -0000 From: Edjunior Barbosa Machado User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10) Gecko/20100619 Lightning/1.0b1 Icedove/3.0.5 MIME-Version: 1.0 To: gdb@sourceware.org Subject: next/step after main() function's return Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-12/txt/msg00079.txt.bz2 Hello, when issuing a next or step after main() function's return statement, gdb drops to __libc_start_main() from libc on x86 (or generic_start_main() on ppc and so on, depending on the arch if I'm not mistaken). Is it considered a bug or it's just the expected behavior? Thanks, -- Edjunior