From: chris@basementcode.com (Christopher Harvey)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Debugging a custom kernel
Date: Thu, 30 Jun 2011 08:12:21 -0500 [thread overview]
Message-ID: <9010b514b542a9cbf4352593059f25cd@basementcode.com> (raw)
In-Reply-To: <20110629212741.GG5604@hermes>
On Wed, 29 Jun 2011 23:27:41 +0200, Apelete Seketeli wrote:
> On 29-Jun-11, Christopher Harvey wrote:
>> On 06/29/11 16:14, Apelete Seketeli wrote:
>> > I still can't
>> > figure where the boot process is getting stuck with step-by-step
>> > execution, but it seems that the last function called is
>> "delay_loop"
>> > from arch/x86/lib/delay.c.
>> Have you run the backtrace (bt) command from the gdb shell? That
>> should
>> tell you what function is calling the __delay.
>
> I didn't, will try that and see if it helps.
That command is your bread and butter. If you type "up" into gdb it
will take you to the line that called __delay. Keep typing up to see
exactly what series of functions were called to get to the __delay.
next prev parent reply other threads:[~2011-06-30 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 20:14 Debugging a custom kernel Apelete Seketeli
2011-06-29 16:41 ` Christopher Harvey
2011-06-29 21:27 ` Apelete Seketeli
2011-06-30 13:12 ` Christopher Harvey [this message]
2011-06-29 20:42 ` Jonathan Neuschäfer
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=9010b514b542a9cbf4352593059f25cd@basementcode.com \
--to=chris@basementcode.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).