* Alan Cox ([email protected]) wrote:
> In addition ideally we want a mechanism that is also sufficient that
> printk can be mangled into so that you can pull all the printk text
> strings _out_ of the kernel and into the debug traces for embedded work.
>
Further on, in LTTng 0.5.113, I added the possibility to trace the location
where the printk happened. Within a huge amount of information, this kind of
data identification can be very useful.
Example of a printk as shown from the text dump of a trace :
kernel.printk_locate: 181.713815470 (/tmp/trace2/cpu_0),
4357, 0, insmod, UNBRANDED, 4234, 0x0, SYSCALL,
{ file = "/home/compudj/repository/tests/kernel/test-printk.c",
function = "init_module", line = 14, address = 0xf88eb000 }
kernel.printk: 181.713817590 (/tmp/trace2/cpu_0),
4357, 0, insmod, UNBRANDED, 4234, 0x0, SYSCALL,
{ loglevel = 0, text = { printk message } }
Regards,
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
