This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [uml-user] problems debugging an uml skas kernel with gdb
- From: "Ramana Radhakrishnan" <ramana dot radhakrishnan at codito dot com>
- To: "Blaisorblade" <blaisorblade at yahoo dot it>
- Cc: user-mode-linux-user at lists dot sourceforge dot net, "marco ghidinelli" <marcogh at linux dot it>, "gdb ml" <gdb at sources dot redhat dot com>
- Date: Thu, 9 Jun 2005 01:16:40 +0530 (IST)
- Subject: Re: [uml-user] problems debugging an uml skas kernel with gdb
- References: <20050608123442.GB8481@localhost.localdomain> <200506081715.07405.blaisorblade@yahoo.it>
- Reply-to: ramana dot radhakrishnan at codito dot com
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