From: Ian Campbell <ian.campbell@citrix.com>
To: kumara rathnavel <kumara.bsd@gmail.com>, xen-devel@lists.xen.org
Subject: Re: Fwd: Fwd: LibXL
Date: Tue, 22 Sep 2015 13:32:31 +0100 [thread overview]
Message-ID: <1442925151.10338.159.camel@citrix.com> (raw)
In-Reply-To: <CA+NzLaNudD7zyJ3JiFzeZnyP66sQhTwOrD9Eg1AyBgj+si6D5Q@mail.gmail.com>
On Tue, 2015-09-22 at 17:19 +0530, kumara rathnavel wrote:
> Hello Ian,
>
> As requested I have attached the gdb output of the code.
You need to build with debugging symbols included, or to avoid stripping
them, otherwise the stack trace just contains interpretable.
If you are unfamiliar with debugging of C code then may I suggest that you
try and find someone local to help/mentor you through the basics.
Ian.
>
> On 22 September 2015 at 15:21, Ian Campbell <ian.campbell@citrix.com>
> wrote:
> > On Tue, 2015-09-22 at 14:50 +0530, kumara rathnavel wrote:
> >
> > > > I have attached my code. I have also attached the system call
> > traces file
> > > > which was generated by the command truss for the command that was
> > > > successful through XL and the other one that failed where I used
> > the call
> > > > directly.
> >
> > I'm afraid that truss is of very little use for debugging these sorts
> > of
> > issues.
> >
> > What you need is to run the program under a debugger (such as gdb) and
> > to
> > get a stack trace from the point of the segfault.
> >
> > Ian.
> >
> >
> >
prev parent reply other threads:[~2015-09-22 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+NzLaPaeXebw6K6j6tkckAYycwo-3Hx3+Kyw0O0pkM5+FVW1A@mail.gmail.com>
[not found] ` <CA+NzLaNJgHrBHOP6BwEGAeSn=+C-aUuJCjm-nxD1M+GNOf6xHA@mail.gmail.com>
[not found] ` <1442911546.10338.111.camel@citrix.com>
2015-09-22 9:20 ` Fwd: Fwd: LibXL kumara rathnavel
2015-09-22 9:51 ` Ian Campbell
2015-09-22 11:49 ` kumara rathnavel
2015-09-22 12:32 ` Ian Campbell [this message]
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=1442925151.10338.159.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=kumara.bsd@gmail.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 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).