From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4FF16086.1030903@xenomai.org> Date: Mon, 02 Jul 2012 10:49:10 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <009c01cd539e$e9f81420$bde83c60$@com> <4FF057F2.7040109@xenomai.org> <03de01cd580a$f9016d70$eb044850$@com> In-Reply-To: <03de01cd580a$f9016d70$eb044850$@com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] ARM, exception #0 ? List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: George Pontis Cc: xenomai@xenomai.org On 07/02/2012 06:27 AM, George Pontis wrote: > on the host. And I _still_ have not been able to coax any detailed > output from the kernel with CONFIG_DEBUG_USER and user_debug=29. I > know that this is declared because an added printk shows that it is > executing the function user_debug_setup in arch/arm/kernel/traps.c > which is dependent on CONFIG_DEBUG_USER. But no additional info shows > after the fault, including the fault from your test application. That is supposed to work. What does /proc/sys/kernel/printk say? On my side, I get: # cat /proc/sys/kernel/printk 7 4 1 7 -- Gilles.