From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: geting weird semi-random panic on kmalloc
Date: Tue, 26 Jun 2012 11:31:01 +0700 [thread overview]
Message-ID: <CAGdaadaZJ2Vd-9j7GHTkqTONvY1E+TD1-ZVTsM6y99b2LF0ujA@mail.gmail.com> (raw)
In-Reply-To: <CA+wR77pkxctOzCxqmYE83ToJgU5JmqzS5RAdWeTnQE=uzVkfEQ@mail.gmail.com>
Hi... :)
On Tue, Jun 26, 2012 at 6:22 AM, NorthPole <morfeas3000@gmail.com> wrote:
> @Mulyadi Santosa
>
> several sources on the net suggested that interactive debuggers on the
> kernel are a bad thing so I pushed it down on the todo kernel-skill stack so
> I dont yet know how to use qemu's gdb with the kernel
it is described in qemu wiki website actually. I found it here:
http://www.elinux.org/Virtual_Development_Board
jump into 'Debug U-Boot" section. Of course, adjust the parameters so
that it boots your kernel name and you invoke the qemu arch of your
choice. The rest is the same.
Other thing that I recall is sometimes Qemu had trouble when debugging
interrupts....or in general things that works periodically.
> Good news is I found the error (not me the folks at batman's irc channel
> did) ?the
>
> memcpy(tvlv+sizeof(struct shortTvlv),value,length*sizeof(uint8_t)); needs to
> be
> memcpy((char *)tvlv+sizeof(struct shortTvlv),value,length*sizeof(uint8_t));
great!! :) casting mistakes, right?
> thanks for the assist everyone and if you have any good tutorials on qemu +
> kernel +gdb i'll be thankfull
>
See above :) google might reveal more IMHO
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2012-06-26 4:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 0:50 geting weird semi-random panic on kmalloc NorthPole
2012-06-22 11:55 ` Jonathan Neuschäfer
2012-06-22 12:06 ` NorthPole
2012-06-22 16:18 ` Mulyadi Santosa
2012-06-22 16:27 ` NorthPole
2012-06-22 16:49 ` Mulyadi Santosa
2012-06-25 23:22 ` NorthPole
2012-06-26 4:31 ` Mulyadi Santosa [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=CAGdaadaZJ2Vd-9j7GHTkqTONvY1E+TD1-ZVTsM6y99b2LF0ujA@mail.gmail.com \
--to=mulyadi.santosa@gmail.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).