From: Philippe Gerum <rpm@xenomai.org>
To: niklaus.giger@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Bug in taskSuspend for user mode vxworks
Date: Sat, 28 Oct 2006 20:03:02 +0200 [thread overview]
Message-ID: <1162058582.4954.37.camel@domain.hid> (raw)
In-Reply-To: <200610281940.10654.niklaus.giger@domain.hid>
On Sat, 2006-10-28 at 19:40 +0200, Niklaus Giger wrote:
> Setting a breakpoint at xnpod_fault_handler and a full backtrace gives me
> (gdb) bt full
> #0 xnpod_fault_handler (fltinfo=0xc1839e18)
> at /mnt/data.ng/hcu/kernel/ppc/linux-2.6.14/include/asm-generic/xenomai/system.h:200
> thread = (xnthread_t *) 0xc0214f40
> #1 0xc0048e90 in xnpod_trap_fault (fltinfo=0xc1839e18)
> at /mnt/data.ng/hcu/kernel/ppc/linux-2.6.14/kernel/xenomai/nucleus/pod.c:2907
> No locals.
> #2 0xc00438f4 in xnarch_trap_fault (event=3246628376, domid=1480937039,
> data=0xc1839f50) at include2/asm/xenomai/bits/init.h:46
> fltinfo = {exception = 0, regs = 0xc1839f50}
> #3 0xc011ffb8 in exception_event (event=3221520296, ipd=0x58454e4f,
> data=0xc1839f50)
> at /mnt/data.ng/hcu/kernel/ppc/linux-2.6.14/arch/ppc/xenomai/hal.c:385
> No locals.
> #4 0xc003fecc in __ipipe_dispatch_event (event=0, data=0xc1839f50)
> at /mnt/data.ng/hcu/kernel/ppc/linux-2.6.14/kernel/ipipe/core.c:668
> start_domain = (struct ipipe_domain *) 0xc0214f40
> this_domain = (struct ipipe_domain *) 0xc0214f40
> evhand = (ipipe_event_handler_t) 0xc0048e90 <xnpod_trap_fault+100>
> pos = (struct list_head *) 0xc0214f40
> npos = (struct list_head *) 0xc01c6540
> flags = 167984
> propagate = 1
> #5 0xc000b02c in do_page_fault (regs=0xc1839f50, address=266719224,
> error_code=0)
> at /mnt/data.ng/hcu/kernel/ppc/linux-2.6.14/arch/ppc/mm/fault.c:119
> vma = (struct vm_area_struct *) 0xff86120
> mm = (struct mm_struct *) 0xc0200260
> info = {si_signo = 1, si_errno = -1071644672, si_code = -1071579136,
> _sifields = {_pad = {0, -1048338784, -1048338608,
> -1071554848, -1070595192, -1048338768, -1073423884, -1048338608, -1070595192, -1048338752, -1073422700,
> 0, 1, -1048338704,
> -1073418440, -1071710208, 14, 1, -1071733764, -1071710208, -1071880896,
> 167984, 0, 16384, -1071880896, -1048338640, -1073479988,
> 0, 0}, _kill = {_pid = 0, _uid = 3246628512}, _timer = {_tid = 0,
> _overrun = -1048338784,
> _pad =
> 0xc1839e94 "Á\203\237PÀ!^àÀ0\003\210Á\203\236°À\004ÙôÁ\203\237PÀ0\003\210Á\203\236ÀÀ\004Þ\224",
> _sigval = {
> sival_int = -1048338608, sival_ptr = 0xc1839f50}, _sys_private
> = -1071554848}, _rt = {_pid = 0, _uid = 3246628512, _sigval = {
> sival_int = -1048338608, sival_ptr = 0xc1839f50}}, _sigchld = {_pid =
> 0, _uid = 3246628512, _status = -1048338608,
> _utime = -1071554848, _stime = -1070595192}, _sigfault = {_addr = 0x0},
> _sigpoll = {_band = 0, _fd = -1048338784}}}
> code = 196609
> is_write = 0
> __func__ = "do_page_fault"
> #6 0xc0003258 in handle_page_fault ()
> No locals.
> (gdb)
This looks like a sane kernel call frame for handling an invalid memory
dereference from user-space. Running the faulting application over GDB
would probably give us more information.
>
--
Philippe.
next prev parent reply other threads:[~2006-10-28 18:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 21:46 [Xenomai-core] Bug in taskSuspend for user mode vxworks Niklaus Giger
2006-10-27 16:38 ` Philippe Gerum
2006-10-28 12:54 ` Niklaus Giger
2006-10-28 17:16 ` Philippe Gerum
2006-10-28 17:40 ` Niklaus Giger
2006-10-28 18:00 ` Philippe Gerum
2006-10-28 18:28 ` Niklaus Giger
2006-10-28 18:03 ` Philippe Gerum [this message]
2006-10-28 18:36 ` Wolfgang Grandegger
2006-10-29 21:02 ` Niklaus Giger
2006-10-29 21:15 ` Philippe Gerum
2006-10-30 7:31 ` Wolfgang Grandegger
2006-10-30 7:09 ` Niklaus Giger
2006-10-31 8:14 ` Wolfgang Grandegger
2006-10-31 18:51 ` Niklaus Giger
2006-10-31 19:02 ` Wolfgang Grandegger
2006-10-31 19:17 ` Niklaus Giger
2006-10-31 20:07 ` Wolfgang Grandegger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1162058582.4954.37.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=niklaus.giger@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.