Re: Debugging kernel modules

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

On Sat, Dec 4, 2010 at 05:19, Dev Null <devnullfin@xxxxxxxxx> wrote:
> Hello,

BTW, is it your daily behaviour to hijack someones' else message
thread? Is it hard for you to press "Compose Mail" button and start
fresh new thread by your own?

> How to debug the running kernel module on any production server?

Do you have the debuginfo or debug symbol of those modules? Then maybe
you can use SystemTap....

> In general, what are the debugging techniques of any running production
> server?

First of all, you have to ask to yourself "why can I found it earlier
on the development server?" lack of stress test? lack of test cases?

Secondly, suppose it is a newly found bug...likely a corner case
bug..... Then before you debug it, if I were you, I will activate
(read: make it the master production) backup server first. Update it
with latest data from current master production. Hopefully ...and it's
a must nowadays I guess...you already prepare somekind of High
Availability setup between those servers.

And then? Same like you debug your casual user space programs. So I
ask you back, how do you usually do that such job?

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux