From: Ian Campbell <ian.campbell@citrix.com>
To: Benjamin Beier <benjamin@desaster-games.com>,
	xen-devel@lists.xensource.com
Cc: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: [BUG][4.5.1]xl cpupool-create segfault (with config file parameter)
Date: Thu, 13 Aug 2015 12:29:34 +0100	[thread overview]
Message-ID: <1439465374.23981.86.camel@citrix.com> (raw)
In-Reply-To: <55CC7BF6.8050002@desaster-games.com>
On Thu, 2015-08-13 at 13:13 +0200, Benjamin Beier wrote:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000418db5 in main_cpupoolcreate (argc=, 
> argv=0x7fffffffda50) at xl_cmdimpl.c:7102
> 7102    xl_cmdimpl.c: No such file or directory.
> (gdb) bt
> #0  0x0000000000418db5 in main_cpupoolcreate (argc=<optimized out>, 
> argv=0x7fffffffda50) at xl_cmdimpl.c:7102
> #1  0x0000000000407c79 in main (argc=2, argv=0x7fffffffda50) at xl.c:361
In "git show RELEASE-4.5.1:tools/libxl/xl_cmdimpl.c" line 7102 is a blank
line. The next line is:
     config = xlu_cfg_init(stderr, config_src);
which might be the culprit but also might not be.
Are you running pristine 4.5.1 or are the (perhaps gentoo added) patches?
Can you figure out what line 7102 of that might be.
> Just tell me if this is a gentoo-only thing and I will open a bug report 
> there.
It's not clear yet, since it might be a backport of a buggy patch, but it's
starting to look a bit that way. Once xl_cmdimpl.c:7102 and the list of
patches is clarified I think we'll know one way or another.
Ian
next prev parent reply	other threads:[~2015-08-13 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 11:03 [BUG][4.5.1]xl cpupool-create segfault (with config file parameter) Benjamin Beier
2015-08-12 11:28 ` Ian Campbell
2015-08-13  9:01   ` Dario Faggioli
2015-08-13 11:13   ` Benjamin Beier
2015-08-13 11:29     ` Ian Campbell [this message]
2015-08-13 12:12       ` Benjamin Beier
2015-08-26 22:25     ` Jim Fehlig
2015-09-01 11:18       ` Ian Campbell
2015-09-01 11:29         ` Ian Jackson
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=1439465374.23981.86.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=benjamin@desaster-games.com \
    --cc=dario.faggioli@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).