[PD-dev] crash (memory leak?) with zexy?

B. Bogart ben at ekran.org
Wed Apr 22 21:28:29 CEST 2009


Hey all,

I'm making a new version of my installation shown in Norway.
Unfortunately the same patch is no longer stable, it dies due to what
looks like a memory leak.

Here is the backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf7ce86b0 (LWP 11242)]
0x08101b03 in list_prepend_list (x=0xa81d140, s=0x8128fb0, argc=768,
argv=0xfff92650) at x_list.c:92
92      x_list.c: No such file or directory.
        in x_list.c
(gdb) bt
#0  0x08101b03 in list_prepend_list (x=0xa81d140, s=0x8128fb0, argc=768,
argv=0xfff92650)
    at x_list.c:92
#1  0x080b232f in outlet_list (x=0xa81d0e0, s=0x8128fb0, argc=768,
argv=0xfff92650) at m_obj.c:428
#2  0x08101ce9 in list_prepend_list (x=0xa81d0a0, s=0x8128fb0, argc=256,
argv=0x96816b8)
    at x_list.c:260
#3  0x080b232f in outlet_list (x=0xa81de18, s=0x8128fb0, argc=256,
argv=0x96816b8) at m_obj.c:428
#4  0xf49e4179 in ?? () from /usr/lib/pd/extra/zexy.pd_linux
#5  0x0a81de18 in ?? ()
#6  0x08128fb0 in s_bang ()
#7  0x00000100 in ?? ()
#8  0x096816b8 in ?? ()
#9  0x08125837 in ?? ()
#10 0xffc99fec in ?? ()
#11 0x00000000 in ?? ()

Seems to me this is happening due to some list functions called by zexy?

I greped through all the zexy objects that output lists, and compared
those matches to my PD patches, and the results are not very telling.

tabdump seems the most likely cause, but I've used the same version in
other patches as many as 2,000,000 times, without noticing an issues.

I'm using zexy 2.1 from svn.

I just did an svn update and compiled a non-stripped zexy.

I'll post back if this issue is not solved.

Has anyone else come across this?

Thanks,
B. Bogart





More information about the Pd-dev mailing list