Le 2011-10-05 à 21:13:00, Mathieu Bouchard a écrit :
Then if you run :
valgrind pd vbap-help.pd
and click around a bit, you get :
Actually that's a different bug than the one you found, but that's a bug anyway, and it's the kind of thing that can cause a crash later (e.g. while closing a patch), though I don't know how to get it to really crash.
I made two mistakes... I forgot to paste that there's an Invalid Write of same size at the same place in the programme, just after the Read... a Write is more dangerous.
The other mistake, of course, is that at one point I switched from trying rvbap-help.pd to trying vbap-help.pd without even noticing. With rvbap-help.pd, I get this crash instead :
Invalid write of size 4 at 0x796DB34: rvbap_bang (rvbap.c:619) by 0x80CA552: outlet_bang (m_obj.c:371) by 0x80CA552: outlet_bang (m_obj.c:371) by 0x80FCB3A: trigger_list (x_connective.c:981) by 0x80FCE26: trigger_float (x_connective.c:1025) by 0x80CA0A6: outlet_float (m_obj.c:397) by 0x80CA0A6: outlet_float (m_obj.c:397) by 0x8079BFD: gatom_bang (g_text.c:585) by 0x807DEC1: gatom_motion (g_text.c:615) by 0x80A9268: canvas_motion (g_editor.c:1821) by 0x80C7765: pd_typedmess (m_class.c:792) by 0x80C734B: pd_typedmess (m_class.c:813) Address 0x461d424 is 4 bytes before a block of size 16 alloc'd at 0x4024F12: calloc (vg_replace_malloc.c:467) by 0x80CB2BC: getbytes (m_memory.c:24) by 0x80CA552: outlet_bang (m_obj.c:371) by 0x80CA552: outlet_bang (m_obj.c:371) by 0x80FCB3A: trigger_list (x_connective.c:981) by 0x80FCE26: trigger_float (x_connective.c:1025) by 0x80CA0A6: outlet_float (m_obj.c:397) by 0x80CA0A6: outlet_float (m_obj.c:397) by 0x8079BFD: gatom_bang (g_text.c:585) by 0x807DEC1: gatom_motion (g_text.c:615) by 0x80A9268: canvas_motion (g_editor.c:1821) by 0x80C7765: pd_typedmess (m_class.c:792)
which might or might not be a copy of the same bug...
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC