From: "Mike C." <miguelmclara@gmail.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
"Ian Campbell" <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xensource.com,
"port-xen@netbsd.org" <port-xen@netbsd.org>
Subject: Re: [Xen-devel] Fwd: NetBSD xl core-dump not working... Memory fault (core dumped)
Date: Tue, 03 Dec 2013 18:14:55 +0000 [thread overview]
Message-ID: <529E1F9F.5040501@gmail.com> (raw)
In-Reply-To: <5283730B.2020900@citrix.com>
On 11/13/13 12:39, Roger Pau Monné wrote:
> On 13/11/13 13:36, Miguel C. wrote:
>> I have the xenkernel debug version but in this case you mean the tool right?
>>
>> I recompile xentools again with debug support pater today or tomorrow and give some more feedback.
>
> I mean that you need to compile the hypervisor with debug=y. Have you
> tried to apply the patch on the link that I've posted to NetBSD source
> and rebuild the kernel?
>
Hi, I've rebuilded with the patch + debug a=ynd tried the xl core dump
again, I still get the same issue!
It really seems to fail close to the end (at least judging for the size
of the files)
GDB seems to show similar output, not sure if the debug option should
give more info?!
(gdb) run
Starting program: /usr/sbin/xl -vf dump-core w2k12 core.dump
Program received signal SIGSEGV, Segmentation fault.
[Switching to LWP 1]
0x00007f7ff7007b45 in xc_domain_dumpcore_via_callback
(xch=0x7f7ff7b0d800, domid=32, 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=32, args=0x7f7fffffdae0,
dump_rtn=0x7f7ff700632c <local_file_dump>) at xc_core.c:860
#1 0x00007f7ff7007fda in xc_domain_dumpcore (xch=0x7f7ff7b0d800,
domid=32, corename=0x7f7ffffffe91 "core.dump") at xc_core.c:983
#2 0x00007f7ff74117b3 in libxl_domain_core_dump (ctx=0x7f7ff7b03200,
domid=32, filename=0x7f7ffffffe91 "core.dump", ao_how=<optimized out>)
at libxl.c:808
#3 0x000000000040f748 in core_dump_domain (filename=0x7f7ffffffe91
"core.dump", domain_spec=<optimized out>) at xl_cmdimpl.c:3301
#4 main_dump_core (argc=<optimized out>, argv=0x7f7fffffdca8) at
xl_cmdimpl.c:3642
#5 0x0000000000407055 in main (argc=3, argv=0x7f7fffffdca8) at xl.c:267
(gdb)
next prev parent reply other threads:[~2013-12-03 18:14 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 ` Fwd: NetBSD xl core-dump not working... Memory fault (core dumped) Mike C.
2013-11-07 10:29 ` 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. [this message]
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=529E1F9F.5040501@gmail.com \
--to=miguelmclara@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=port-xen@netbsd.org \
--cc=roger.pau@citrix.com \
--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).