Re: [Xenomai-help] address spaces of real-time task and standard linux process

[Tom Z <tomz30@domain.hid>]

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]



Thanks. I increased the stack size and the problem was gone. This problem was hard to find for me, as when I step into the functions in gdb, the locations where the problem occurs are different.


BTW, in your previous reply you mentioned debugging techniques such as examining the registers and disassembling, can you suggesting some readings that elaborate such techniques. I have a few questions regarding such techniques, e.g., how do I interpret the meaning of each register? By disassembling, do you mean looking at the assembly codes?


Thanks,
Tom



________________________________
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.orgmai.org>
To: Tom Z <tomz30@domain.hid>
Cc: Thomas Lockhart <Thomas.Lockhart@domain.hid>; "xenomai@xenomai.org" <xenomai@xenomai.org>
Sent: Tuesday, 25 October 2011 5:50 AM
Subject: Re: [Xenomai-help] address spaces of real-time task and standard linux process

On 10/24/2011 11:04 PM, Tom Z wrote:
>  8)     rt_task_create(&task_desc, "RealTimeImageProcessing", 4096, 99, T_FPU|T_CPU(0));

4096 bytes is a really small stack size, are you sure that the
segmentation fault is simply not a stack overflow?

-- 
                        Gilles.

[-- Attachment #2: Type: text/html, Size: 2068 bytes --]