From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6708 invoked by alias); 27 Dec 2009 03:36:40 -0000 Received: (qmail 6700 invoked by uid 22791); 27 Dec 2009 03:36:40 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 27 Dec 2009 03:36:36 +0000 Received: from wpaz17.hot.corp.google.com (wpaz17.hot.corp.google.com [172.24.198.81]) by smtp-out.google.com with ESMTP id nBR3aWPg030758 for ; Sun, 27 Dec 2009 03:36:32 GMT Received: from qw-out-2122.google.com (qwh8.prod.google.com [10.241.194.200]) by wpaz17.hot.corp.google.com with ESMTP id nBR3aUhi002067 for ; Sat, 26 Dec 2009 19:36:31 -0800 Received: by qw-out-2122.google.com with SMTP id 8so624092qwh.33 for ; Sat, 26 Dec 2009 19:36:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.224.23.131 with SMTP id r3mr6904114qab.273.1261884990804; Sat, 26 Dec 2009 19:36:30 -0800 (PST) In-Reply-To: References: <8ac60eac0912260055o2d6bcb6cld7f8830e947cdd7@mail.gmail.com> Date: Sun, 27 Dec 2009 03:36:00 -0000 Message-ID: <8ac60eac0912261936q49f50cf6ofabf2c56055621af@mail.gmail.com> Subject: Re: gdb symbol problem From: Paul Pluzhnikov To: Hushan Jia Cc: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-System-Of-Record: true 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: 2009-12/txt/msg00163.txt.bz2 On Sat, Dec 26, 2009 at 6:16 PM, Hushan Jia wrote: > I invoke gdb like this: > > [hushan@hushan-t linux-2.6.31.3]$ gdb ./vmlinux Oh, you are not debugging a regular application. You probably should have mentioned that in your initial message. > (gdb) target remote /dev/pts/5 What is on the "other end" of /dev/pts/5 ? >> My crystal ball tells me you didn't supply GDB with the executable you >> are running. My crystal ball now tells me that you are stopped in a loadable kernel module. AFAIU, GDB has no way to automatically find what is loaded where in the target kernel. You might want to read: http://sourceforge.net/projects/kgdb-light/ http://sourceware.org/ml/gdb/2009-01/msg00037.html Cheers, -- Paul Pluzhnikov