Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ramana Radhakrishnan" <ramana.radhakrishnan@codito.com>
To: "Blaisorblade" <blaisorblade@yahoo.it>
Cc: user-mode-linux-user@lists.sourceforge.net,
	"marco ghidinelli" <marcogh@linux.it>,
	"gdb ml" <gdb@sources.redhat.com>
Subject: Re: [uml-user] problems debugging an uml skas kernel with gdb
Date: Wed, 08 Jun 2005 19:54:00 -0000	[thread overview]
Message-ID: <3242.203.212.198.158.1118260000.squirrel@webmail.codito.com> (raw)
In-Reply-To: <200506081715.07405.blaisorblade@yahoo.it>


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


      reply	other threads:[~2005-06-08 19:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 12:35 marco ghidinelli
2005-06-08 15:11 ` [uml-user] " Blaisorblade
2005-06-08 19:54   ` Ramana Radhakrishnan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3242.203.212.198.158.1118260000.squirrel@webmail.codito.com \
    --to=ramana.radhakrishnan@codito.com \
    --cc=blaisorblade@yahoo.it \
    --cc=gdb@sources.redhat.com \
    --cc=marcogh@linux.it \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox