From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15363 invoked by alias); 10 Jun 2005 18:00:34 -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 15324 invoked by uid 22791); 10 Jun 2005 18:00:27 -0000 Received: from ext-nj2gw-6.online-age.net (HELO ext-nj2gw-6.online-age.net) (64.14.56.42) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 10 Jun 2005 18:00:27 +0000 Received: from int-nj2gw-4.online-age.net (int-nj2gw-4 [3.159.236.68]) by ext-nj2gw-6.online-age.net (8.12.11/8.12.11/990426-RLH) with ESMTP id j5AI0NgX016848 for ; Fri, 10 Jun 2005 14:00:26 -0400 Received: from uswaumsxb4medge.am.med.ge.com (localhost [127.0.0.1]) by int-nj2gw-4.online-age.net (8.12.9/8.12.8/990426-RLH) with ESMTP id j5AI0Ms6008439 for ; Fri, 10 Jun 2005 14:00:23 -0400 (EDT) Received: from uswaumsxb3medge.am.med.ge.com (uswaumsxb3medge.med.ge.com [3.57.24.74]) by uswaumsxb4medge.am.med.ge.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id MRM1B9W4; Fri, 10 Jun 2005 13:00:22 -0500 Received: from gsao.gso.med.ge.com (uswaucs03 [3.57.24.237]) by uswaumsxb3medge.am.med.ge.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id MPJN5ZC4; Fri, 10 Jun 2005 13:00:22 -0500 Received: from godzilla (IDENT:12539@godzilla [3.70.204.208]) by gsao.gso.med.ge.com (8.12.10+Sun/8.12.10) with ESMTP id j5AI1Amk027885 for ; Fri, 10 Jun 2005 13:01:11 -0500 (CDT) Date: Fri, 10 Jun 2005 18:00:00 -0000 From: Rich Coe To: gdb@sources.redhat.com Subject: no stack trace with 2.6.11 and gdb 6.3 Message-ID: <20050610125855.62ce7313@godzilla> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2005-06/txt/msg00092.txt.bz2 I have been investigating a problem we found here, which initially exactly matched the problem reported here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=146087 1. Start a 32-bit app on a x86_64 system 2. attach with gdb 3. backtrace starting in a system call doesn't work Our versions: kernel: 2.6.11.11 gdb: 6.3.0.0-1.21 After reviewing the patch made to bug#146087, I found that I can get a valid traceback if I issue the following request: add-symbol-file-from-memory 0xffffe000 The interesting part is that this also failing on x86 systems, not just x86_64. If you start an application from within gdb on the command line, the following line is printed out: Loaded system supplied DSO at 0xffffe000 Which is apparently some internal gdb function executing the 'add-symbol-file-from-memory' request that does not happen when attaching to a running process. I have a linux-2.6.7 system with gdb 6.0post-0.20040223.19rh that doesn't have this problem. We have also replicated this problem on a current FC3 standard distribution with gdb-6.3.0.0-1.21. The latest/last FC3 gdb shows the problem noted in the bug report identified above. How did we get this problem from gdb 6.0 to gdb 6.3 ? -- Rich Coe richard.coe@med.ge.com General Electric Healthcare Technologies Global Software Platforms, Computer Technology Team