Just some brief statement from a patch by Mathieu - explaining the
meaning of tracepoints. (semantically, it should be similar to
kernel markers, right?)
On Wed, Jul 16, 2008 at 6:26 AM, Mathieu Desnoyers
<[EMAIL PROTECTED]> wrote:
> Implementation of kernel tracepoints. Inspired from the Linux
This is awesome. Kernel debugging over serial port is well known.
But debugging over USB and other ports are also:
This is for Firewire:
http://osdir.com/ml/kernel.debugging.kgdb.bugs/2006-03/msg00069.html
And for USB I cannot findbut today there is a kernel patch related to that:
http://
Hi, Arn,
so have u done anything so far? Frankly, i don't understand what is
the purpose of MMU notification patch - anyone can explain?
For example, one particular explanation is given here:
http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-01/msg04810.html
So my question is: is the "sh
Lot of free courses here:
http://tuxology.net/
(but if u go to free-electron.org, u may be able to get the materials
as wellnot sure...but does not matter).
Example of online courses:
Linux Kernel Internals
Linux Network Internal
Embedded Advanced Linux (241 pages).
etc.
And there is a co
Just want to share this.
First, at:
http://tuxology.net/lectures/crash-and-burn-writing-linux-application-fault-handlers/
At page 6, is the common practise of capturing the stacktrace,
whenever error occurred. But this is actually wrong, and will give
rise to race condition.
Inside the signal
Hi!
I am learning linkux kernel internals and facing the following problem:
1. I use __bread to read a fixed place block on a block drive.
2. I use submit_bio to read/write data on the same drive. The order the
data is written may be arbitrary and, in general, it almost never occur
at the sam
Hi,
How can analyze a dump of memory?
I get this dump from the running of the following command:
# dd if = / dev / mem of = / root / memory.dump
# file memory.dump
memory.dump Date
I can only use the command strings associated with grep.
Is there any other kind of analysis?
Can I get this inf
Sorryi don't understand what u meant :-):
On Sat, Jul 26, 2008 at 8:39 PM, Mulyadi Santosa
<[EMAIL PROTECTED]> wrote:
> NB: Anyway, I just found out that we know have ftrace in latest kernel...
>
what is this ftrace to do with the present discussion? I am really
eager to learn this thing...
Hi,
"Mulyadi Santosa" <[EMAIL PROTECTED]> writes:
> Gr :)
>
> Peter is right and I forgot one simple fact: Elad might compile his
> kernel without frame pointer being used to mark the start of local
> variables :) hehehe, sorry for that.
>
> Anyway, bottom line, that's just makes you harder t
Peteras you all know, is like walking dictionary. ManI owe much! :D
NB: Anyway, I just found out that we know have ftrace in latest kernel...
regards,
Mulyadi.
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the FAQ at ht
Gr :)
Peter is right and I forgot one simple fact: Elad might compile his
kernel without frame pointer being used to mark the start of local
variables :) hehehe, sorry for that.
Anyway, bottom line, that's just makes you harder to guess where the
ret addr is. By observing the function prototy
Looking at my kernel:
On Sat, Jul 26, 2008 at 10:57 AM, Mulyadi Santosa
<[EMAIL PROTECTED]> wrote:
> Hi Elad...
>
> On Fri, Jul 25, 2008 at 4:03 AM, Elad Lahav
> <[EMAIL PROTECTED]> wrote:
>> I am trying to determine, in run-time, the where a function was called from.
>> I believe that the standa
Check this out:
http://tldp.org/HOWTO/Linux-i386-Boot-Code-HOWTO/index.html
May be correct, incorrect - verify and share with us, and if u are on
embedded, why not write one for other port, and share herepossibly
someone can refine it till it gets good enough to go into the HOWTO?
On Thu, J
13 matches
Mail list logo