From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27997 invoked by alias); 8 Jun 2005 19:54:23 -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 27990 invoked by uid 22791); 8 Jun 2005 19:54:21 -0000 Received: from 203.197.88.2.ill-pune.static.vsnl.net.in (HELO marvin.codito.net) (203.197.88.2) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 08 Jun 2005 19:54:21 +0000 Received: from webmail.codito.com (localhost [127.0.0.1]) by marvin.codito.net (8.13.4/8.13.4/Debian-2) with ESMTP id j58JkbhT019496; Thu, 9 Jun 2005 01:16:40 +0530 Received: from 203.212.198.158 (SquirrelMail authenticated user ramana.radhakrishnan) by webmail.codito.com with HTTP; Thu, 9 Jun 2005 01:16:40 +0530 (IST) Message-ID: <3242.203.212.198.158.1118260000.squirrel@webmail.codito.com> In-Reply-To: <200506081715.07405.blaisorblade@yahoo.it> References: <20050608123442.GB8481@localhost.localdomain> <200506081715.07405.blaisorblade@yahoo.it> Date: Wed, 08 Jun 2005 19:54:00 -0000 Subject: Re: [uml-user] problems debugging an uml skas kernel with gdb From: "Ramana Radhakrishnan" To: "Blaisorblade" Cc: user-mode-linux-user@lists.sourceforge.net, "marco ghidinelli" , "gdb ml" Reply-To: ramana.radhakrishnan@codito.com User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Status: Clean X-SW-Source: 2005-06/txt/msg00073.txt.bz2 Hey, >> the problems are: >> >> 1) a pointer to a struct was not seen by the debugger: >> >> example session: >> >> Breakpoint 4, yoghi_init (sch=0x9d1b830, opt=0x9d1b400) >> at net/sched/sch_yoghi.c:235 >> 235 printk(KERN_DEBUG "Yoghi 0.0.3 Initiaziled\n"); >> (gdb) n >> Yoghi 0.0.3 Initiaziled >> 236 if(q != NULL) >> (gdb) n >> 237 printk(KERN_DEBUG "yoghi_init: q = >> 0x%x\n",(u32)q); >> (gdb) n >> yoghi_init: q = 0x9d1b480 >> 238 return 0; >> (gdb) p q >> No symbol "q" in current context. You might want to show the entire source and the assembly generated as well. Even better see if you can narrow it down to a testcase . We dont have enough information to know whats going on here. Maybe you can try and pare it down to a smaller testcase (better) or send the disassembly over (of the affected function) with its source if possible .There are a couple of situations when gdb can get lost. cheers Ramana ---- Ramana Radhakrishnan Codito Technologies