From: Christopher Li <sparse@chrisli.org>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Best way to inspect the parse tree from Sparse
Date: Wed, 9 Aug 2017 14:41:02 -0400 [thread overview]
Message-ID: <CANeU7QmpT1-zEXmxtesaicD+W_dwMMxODno7og+5C6tuBFimpQ@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxfrgT1Q9X5B7iw=+zYA7bO4uchBo8txqsqnBw-xf+2C_A@mail.gmail.com>
On Wed, Aug 9, 2017 at 1:42 PM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
> I built the latest version (master branch) - and tried to run it. It
> immediately crashes with core dump as soon as I click on anything.
Hmm, works for me on Fedora 26.
Do you have gtk2-devel installed? In Ubuntu it should be libgtk2.0-dev.
Did you give it a C file to parse. e.g. ./test-inspect parse.c
You can also do a gdb on the test-inspect and report back what
back trace do you get. My wild guess is that, it is got some incomparable
library or some thing.
Too bad it is not working for you, otherwise it should be the better one
that show the AST tree nodes.
Chris
next prev parent reply other threads:[~2017-08-09 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 15:11 Best way to inspect the parse tree from Sparse Dibyendu Majumdar
2017-08-07 15:19 ` Christopher Li
2017-08-07 18:46 ` Luc Van Oostenryck
2017-08-07 23:35 ` Christopher Li
2017-08-09 17:14 ` Dibyendu Majumdar
2017-08-09 17:42 ` Dibyendu Majumdar
2017-08-09 18:41 ` Christopher Li [this message]
2017-08-09 18:47 ` Dibyendu Majumdar
2017-08-09 19:22 ` Christopher Li
2017-08-09 19:46 ` Dibyendu Majumdar
2017-08-09 19:57 ` Christopher Li
2017-08-09 20:03 ` Dibyendu Majumdar
2017-08-09 20:21 ` Christopher Li
2017-08-10 19:59 ` Christopher Li
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=CANeU7QmpT1-zEXmxtesaicD+W_dwMMxODno7og+5C6tuBFimpQ@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=mobile@majumdar.org.uk \
/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).