Re: [Vala] segfault test case

[Martin Olsson <mnemo minimum se>]

Thanks for the bug report Frédéric.

I was also able to repro this crash using vala trunk as to feb 9th.
To make sure this bug isn't lost I've filed it (plus info
from below) in the gnome bugtracker here:

http://bugzilla.gnome.org/show_bug.cgi?id=571037

---

(note: putting the code into a single .vala file makes the bug go away)

The backtrace is a near endless list of frames like these:

#0  0x00007ff47ad15990 in _int_memalign () from /lib/libc.so.6
#1  0x00007ff47ad16b04 in memalign () from /lib/libc.so.6
#2  0x00007ff47ad16d08 in posix_memalign () from /lib/libc.so.6
#3  0x00007ff47b063941 in slab_allocator_alloc_chunk (chunk_size=96) at 
/build/buildd/glib2.0-2.19.6/glib/gslice.c:1136
#4  0x00007ff47b064af3 in IA__g_slice_alloc (mem_size=88) at /build/buildd/glib2.0-2.19.6/glib/gslice.c:666
#5  0x00007ff47b064be6 in IA__g_slice_alloc0 (mem_size=140688012376576) at 
/build/buildd/glib2.0-2.19.6/glib/gslice.c:833
#6  0x00007ff47b301490 in IA__g_type_create_instance (type=18480224) at 
/build/buildd/glib2.0-2.19.6/gobject/gtype.c:1654
#7  0x00007ff47b682a1d in gee_array_list_real_iterator (base=0x18d2b60) at arraylist.c:365
#8  0x00007ff47b5e794b in vala_code_context_find_cycle_head (self=0x118e020, file=0x118e360) at 
valacodecontext.c:371
#9  0x00007ff47b5e79fb in vala_code_context_find_cycle_head (self=0x118e020, file=0x118e290) at 
valacodecontext.c:380
#10 0x00007ff47b5e79fb in vala_code_context_find_cycle_head (self=0x118e020, file=0x118e360) at 
valacodecontext.c:380
#11 0x00007ff47b5e79fb in vala_code_context_find_cycle_head (self=0x118e020, file=0x118e290) at 
valacodecontext.c:380
#12 0x00007ff47b5e79fb in vala_code_context_find_cycle_head (self=0x118e020, file=0x118e360) at 
valacodecontext.c:380
...
#35934 0x00007fef96a759fb in vala_code_context_find_cycle_head (self=0x1673020, file=0x1673360) at 
valacodecontext.c:380
#35935 0x00007fef96a759fb in vala_code_context_find_cycle_head (self=0x1673020, file=0x1673290) at 
valacodecontext.c:380
#35936 0x00007fef96a759fb in vala_code_context_find_cycle_head (self=0x1673020, file=0x1673360) at 
valacodecontext.c:380
#35937 0x00007fef96a759fb in vala_code_context_find_cycle_head (self=0x1673020, file=0x1673290) at 
valacodecontext.c:380


While running it in nemiver, basically vala_code_context_find_cycle_head calls itself
on line 380 once the inner while loop reaches its second iteration. FWIW, if the alternating
file=BLAH pointer is dereferenced (and also its "priv" field) inside it then what
I see is that the filename field is set to the same thing in the 0x1673290 object and
the 0x1673360 object.



                Martin


Frédéric Gaudy wrote:
> Hi,
>
> I've got a segfault with this command : valac -C test2.vala test1.vala
>
> I'm using vala 0.5.6.
>
> Thanks.
>
> ------------------------------------------------------------------------
> Ne pleurez pas si votre Webmail ferme. Récupérez votre historique sur 
> Yahoo! Mail 
> <http://fr.rd.yahoo.com/mail_fr/taglines/caramail/*http://fr.docs.yahoo.com/mail/transfert_mails.html>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Vala-list mailing list
> Vala-list gnome org
> http://mail.gnome.org/mailman/listinfo/vala-list