On Wed, Sep 2, 2009 at 6:08 PM, Manish Katiyar wrote:
> Hi,
>
> I was going through this post
> http://kerneltrap.org/mailarchive/linux-kernel/2008/1/8/546623 and
> couldn't understand the steps around the below paragraph.
>
> "
> and run it under gdb, and then when it gets the SIGSEGV (due to the
was in the midst of writing my final installment of newbie column
for how to use /proc sequence files for debugging, and suddenly i'm
not convinced i know every detail about them. in particular, i'm
looking at the prototype for the "stop" routine:
void stop(struct seq_file* s, void* v);
and
Madhavi Manchala writes:
...
> http://www.cyberciti.biz/tips/linux-netconsole-log-management-tutorial.html
>
> I tried to load the netconsole with the following command in FC-8 and
> FC-10 systems.
>
> # modprobe netconsole
> 6...@192.168.1.5/eth0,5...@192.168.1.100/00:19:D1:2A:BA:A8
>
> I got t
Manish Katiyar writes:
> Hi,
>
> I was going through this post
> http://kerneltrap.org/mailarchive/linux-kernel/2008/1/8/546623 and
> couldn't understand the steps around the below paragraph.
>
> "
> and run it under gdb, and then when it gets the SIGSEGV (due to the
> obvious NULL pointer derefe
Hi,
I was going through this post
http://kerneltrap.org/mailarchive/linux-kernel/2008/1/8/546623 and
couldn't understand the steps around the below paragraph.
"
and run it under gdb, and then when it gets the SIGSEGV (due to the
obvious NULL pointer dereference), I can just ask gdb to disassemble
NIdhi,
On Wed, Sep 2, 2009 at 2:45 PM, nidhi mittal
hada wrote:
>
> Hi All
> "I am writing for learning purpose a basic filesystem that just mounts
> loads super block and root inode from disk."
>
> Now i am facing a problem
> when i do
>
> mount -t myfs2 utils/nnn /mnt -o loop - it stucks he
On Wed, 2009-09-02 at 15:17 +0530, Anuz Pratap Singh Tomar wrote:
> On Wed, Sep 2, 2009 at 2:30 PM, Bernd Petrovitsch
> wrote:
> On Wed, 2009-09-02 at 13:31 +0530, Anuz Pratap Singh Tomar
> wrote:
> > that part of code wont be executed.
[...]
> Then why not simply
> Then why not simply use "do { } while (0)" or similar?
> [...]
> > can someone please explain me the meaning/benefits of the "if
> > (0)" statement?
(Probably) it is used to avoid "unused variable" message during
compilation.
regards,
Matteo
--
A full belly makes a dull brain
On Wed, Sep 2, 2009 at 2:30 PM, Bernd Petrovitsch wrote:
> On Wed, 2009-09-02 at 13:31 +0530, Anuz Pratap Singh Tomar wrote:
> > that part of code wont be executed.
>
> Please don't top-post.
>
> My mail client sucked, will take care. du'h!
> Then why not simply use "do { } while (0)" or simila
Hi All
"I am writing for learning purpose a basic filesystem that just mounts
loads super block and root inode from disk."
Now i am facing a problem
when i do
mount -t myfs2 utils/nnn /mnt -o loop - it stucks here
then doing
ps -ax | grep -i mountshows themount script is in RL
On Wed, 2009-09-02 at 13:31 +0530, Anuz Pratap Singh Tomar wrote:
> that part of code wont be executed.
Please don't top-post.
Then why not simply use "do { } while (0)" or similar?
[
> On Wed, Sep 2, 2009 at 1:24 PM, luca ellero wrote:
[...]
> can someone please explain me the meanin
that part of code wont be executed.
On Wed, Sep 2, 2009 at 1:24 PM, luca ellero wrote:
> Hi all,
>
> looking into kernel source code (2.6.26.8) I encountered this definition
> (in include/linux/kernel.h):
>
> #ifdef DEBUG
> /* If you are writing a driver, please use dev_dbg instead */
> #define
Hi all,
looking into kernel source code (2.6.26.8) I encountered this definition
(in include/linux/kernel.h):
#ifdef DEBUG
/* If you are writing a driver, please use dev_dbg instead */
#define pr_debug(fmt, arg...) \
printk(KERN_DEBUG fmt, ##arg)
#else
#define pr_debug(fmt, arg...) \
13 matches
Mail list logo
