From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14735 invoked by alias); 15 Feb 2005 14:35:28 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 14619 invoked from network); 15 Feb 2005 14:35:19 -0000 Received: from unknown (HELO conterra.de) (212.124.44.162) by sourceware.org with SMTP; 15 Feb 2005 14:35:19 -0000 Received: from localhost (unknown [127.0.0.1]) by conterra.de (-) with ESMTP id DCB0D1C88DD for ; Tue, 15 Feb 2005 15:35:18 +0100 (CET) Message-ID: <421208A4.7060607@conterra.de> Date: Wed, 16 Feb 2005 02:10:00 -0000 From: =?ISO-8859-1?Q?Dieter_St=FCken?= MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: 'next' command broken on sparc Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2005-02/txt/msg00105.txt.bz2 I frequently observe the 'next' command not to stop at then next line. Instead the program continues to the end. Similar problems are reported some time ago in conjunction with mips, threads or shlibs. But I'm working on solaris, using: GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.8". and: > gcc -v Reading specs from /share/unix/solaris/8/pakete/gcc-3.4.3-64/lib/gcc/sparc64-sun-solaris2.8/3.4.3/specs Configured with: ../gcc-3.4.3/configure --prefix=/share/unix/solaris/8/pakete/gcc-3.4.3-64 sparc64-sun-solaris2.8 Thread model: posix gcc version 3.4.3 It happens in a bigger project, and I could not narrow it down to special situations. It seems to happen quite randomly to me. Thus I don't have any small example code by now. I have to use shared libs, which also require threads (although I don't use any threads explicitly) Is this a known problem? Can I avoid it? Dieter. -- Dieter Stüken, con terra GmbH, Münster stueken@conterra.de http://www.conterra.de/ (0)251-7474-501