From: "Mike C." <miguelmclara@gmail.com>
To: xen-devel@lists.xensource.com,
"port-xen@netbsd.org" <port-xen@netbsd.org>
Subject: Fwd: NetBSD xl core-dump not working... Memory fault (core dumped)
Date: Mon, 04 Nov 2013 22:13:59 +0000 [thread overview]
Message-ID: <52781C27.2040508@gmail.com> (raw)
In-Reply-To: <52770EED.9090804@gmx.de>
On 31.10.13 04:34, Miguel Clara wrote:
> I was trying to get a core-dump for a domU with xl and got this error:
>
> # xl dump-core 20 test.core
> Memory fault
>
> GDB shows this:
>
> a# gdb xl xl.core
> GNU gdb (GDB) 7.3.1
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later<http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64--netbsd".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /usr/sbin/xl...done.
> [New process 1]
> Core was generated by `xl'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x00007f7ff7007b45 in xc_domain_dumpcore_via_callback
> (xch=0x7f7ff7b0d800, domid=20, args=0x7f7fffffdae0,
> dump_rtn=0x7f7ff700632c<local_file_dump>)
> at xc_core.c:860
> 860 xc_core.c: No such file or directory.
> in xc_core.c
>
>
> (gdb) backtrace
> #0 0x00007f7ff7007b45 in xc_domain_dumpcore_via_callback
> (xch=0x7f7ff7b0d800, domid=20, args=0x7f7fffffdae0,
> dump_rtn=0x7f7ff700632c<local_file_dump>)
> at xc_core.c:860
> #1 0x00007f7ff7007fda in xc_domain_dumpcore (xch=0x7f7ff7b0d800,
> domid=20, corename=0x7f7ffffffe78 "test.core") at xc_core.c:983
> #2 0x00007f7ff74117b3 in libxl_domain_core_dump (ctx=0x7f7ff7b03200,
> domid=20, filename=0x7f7ffffffe78 "test.core", ao_how=<optimized out>)
> at libxl.c:808
> #3 0x000000000040f748 in core_dump_domain (filename=0x7f7ffffffe78
> "test.core", domain_spec=<optimized out>) at xl_cmdimpl.c:3301
> #4 main_dump_core (argc=<optimized out>, argv=0x7f7fffffdca0) at
> xl_cmdimpl.c:3642
> #5 0x0000000000407055 in main (argc=3, argv=0x7f7fffffdca0) at xl.c:267
>
I think, xen-devel is the right list for this.
It's ok to cross-post to keep NetBSD people involved for answering
NetBSD specific questions from the Xen/Citrix people that would
be not answered, otherwise.
Christoph
next parent reply other threads:[~2013-11-04 22:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52770EED.9090804@gmx.de>
2013-11-04 22:13 ` Mike C. [this message]
2013-11-07 10:29 ` Fwd: NetBSD xl core-dump not working... Memory fault (core dumped) Ian Campbell
2013-11-07 21:04 ` [Xen-devel] " Miguel C.
2013-11-08 10:29 ` Ian Campbell
2013-11-08 17:20 ` John Nemeth
2013-11-12 9:35 ` Ian Campbell
2013-11-13 21:31 ` James Harper
2013-11-12 9:48 ` [Xen-devel] " Roger Pau Monné
2013-11-12 10:00 ` Ian Campbell
2013-11-12 10:09 ` Roger Pau Monné
2013-11-13 12:36 ` [Xen-devel] " Miguel C.
2013-11-13 12:39 ` Roger Pau Monné
2013-11-13 17:59 ` Miguel C.
2013-12-03 18:14 ` Mike C.
2013-12-10 8:21 ` James Harper
2013-12-10 9:27 ` [Xen-devel] " James Harper
2013-12-10 10:41 ` Andrew Cooper
2013-12-10 10:46 ` James Harper
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=52781C27.2040508@gmail.com \
--to=miguelmclara@gmail.com \
--cc=port-xen@netbsd.org \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).