Re: Best way to inspect the parse tree from Sparse

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Chris,

Yes I do have libgtk-2.0-dev installed as otherwise it would not build.

On 9 August 2017 at 19:41, Christopher Li <sparse@xxxxxxxxxxx> wrote:
> 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.
>

Here is the back trace from gdb:

Starting program: /home/dylan/github/linux-sparse/test-inspect parse.c
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffede40700 (LWP 19249)]
[New Thread 0x7fffed63f700 (LWP 19250)]
[New Thread 0x7fffece3e700 (LWP 19251)]

Thread 1 "test-inspect" received signal SIGSEGV, Segmentation fault.
ast_iter_n_children (tree_model=0x725400, iter=0x0) at ast-model.c:404
404        AstNode  *node = iter->user_data;

Regards
Dibyendu
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux