All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: NULL pointer dereference at at libxlu_cfg.c:356
Date: Wed, 29 Apr 2015 13:35:56 +0300	[thread overview]
Message-ID: <5540B40C.2050301@bitdefender.com> (raw)
In-Reply-To: <5540B33A.70606@citrix.com>

On 04/29/2015 01:32 PM, Andrew Cooper wrote:
> On 29/04/15 11:26, Razvan Cojocaru wrote:
>> (gdb) p list->values[entry]
>> $2 = (XLU_ConfigValue *) 0x0
> 
> As it turns out, the very top commit in staging is a fix for this bug.

I see, sorry for the noise.


Thanks,
Razvan

  reply	other threads:[~2015-04-29 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 10:26 NULL pointer dereference at at libxlu_cfg.c:356 Razvan Cojocaru
2015-04-29 10:32 ` Andrew Cooper
2015-04-29 10:35   ` Razvan Cojocaru [this message]
2015-04-30  0:57 ` Wei Liu

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=5540B40C.2050301@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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.