hi miller, hi all...
if you have this patch:
key | |atom|
deleting the atom will crash pd:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 8136)] 0x08090581 in atom_string (a=0x8364c18, buf=0xbffff040 "0", bufsize=1000) at m_atom.c:89 89 for (sp = a->a_w.w_symbol->s_name, len = 0, quote = 0; *sp; sp++, len++)(gdb) where #0 0x08090581 in atom_string (a=0x8364c18, buf=0xbffff040 "0", bufsize=1000) at m_atom.c:89 #1 0x080912c8 in binbuf_gettext (x=0x835af50, bufp=0x83602e8, lengthp=0x83602ec) at m_binbuf.c:227 #2 0x08060a9c in rtext_retext (x=0x83602e8) at g_rtext.c:279 #3 0x080594e6 in glist_retext (glist=0x835ad60, y=0x835d8b8) at g_graph.c:142#4 0x0805d3e6 in gatom_redraw (client=0x835d8b8, glist=0x835ad60) at g_text.c:452 #5 0x080993ff in sys_flushqueue () at s_inter.c:736 #6 0x08099476 in sys_poll_togui () at s_inter.c:761 #7 0x080995df in sys_pollgui () at s_inter.c:816 #8 0x080963db in m_scheduler () at m_sched.c:486 #9 0x08096c32 in sys_main (argc=1, argv=0xbffff614) at s_main.c:337 #10 0x0809ceca in main (argc=1, argv=0xbffff614) at s_entry.c:29
the workaround is to delete the connection before deleting the object ... still it's a bug ...
any idea?
cheers ... tim
hello,
i noticed this problem with pd0.38 test4 . but i don't have problem anymore with newer pd version...
are you sure using the newest pd version?
cyrille
Tim Blechmann wrote:
hi miller, hi all...
if you have this patch:
key | |atom|
deleting the atom will crash pd:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 8136)] 0x08090581 in atom_string (a=0x8364c18, buf=0xbffff040 "0", bufsize=1000) at m_atom.c:89 89 for (sp = a->a_w.w_symbol->s_name, len = 0, quote = 0; *sp; sp++, len++)(gdb) where #0 0x08090581 in atom_string (a=0x8364c18, buf=0xbffff040 "0", bufsize=1000) at m_atom.c:89 #1 0x080912c8 in binbuf_gettext (x=0x835af50, bufp=0x83602e8, lengthp=0x83602ec) at m_binbuf.c:227 #2 0x08060a9c in rtext_retext (x=0x83602e8) at g_rtext.c:279 #3 0x080594e6 in glist_retext (glist=0x835ad60, y=0x835d8b8) at g_graph.c:142#4 0x0805d3e6 in gatom_redraw (client=0x835d8b8, glist=0x835ad60) at g_text.c:452 #5 0x080993ff in sys_flushqueue () at s_inter.c:736 #6 0x08099476 in sys_poll_togui () at s_inter.c:761 #7 0x080995df in sys_pollgui () at s_inter.c:816 #8 0x080963db in m_scheduler () at m_sched.c:486 #9 0x08096c32 in sys_main (argc=1, argv=0xbffff614) at s_main.c:337 #10 0x0809ceca in main (argc=1, argv=0xbffff614) at s_entry.c:29
the workaround is to delete the connection before deleting the object ... still it's a bug ...
any idea?
cheers ... tim
i noticed this problem with pd0.38 test4 . but i don't have problem anymore with newer pd version...
are you sure using the newest pd version?
recent devel ...
i had a look at the 8000 lines of diffs between devel_ and stable_ ... i found that the setting saver wasn't up to date in devel_
anyway, not related to that segfault ...
and testing 0.38-0, i do get a similar segfault: 0x080a4f6b in atom_string (a=0x0, buf=0xbfffeb50 "0", bufsize=1000) at m_atom.c:89 89 for (sp = a->a_w.w_symbol->s_name, len = 0, quote = 0; *sp; sp++, len++)(gdb) where #0 0x080a4f6b in atom_string (a=0x0, buf=0xbfffeb50 "0", bufsize=1000) at m_atom.c:89 #1 0x080a59ac in binbuf_gettext (x=0x1795, bufp=0x2, lengthp=0x2) at m_binbuf.c:211 #2 0x0806335d in rtext_retext (x=0x8271928) at g_rtext.c:279 #3 0x080b0c8e in sys_pollgui () at s_inter.c:708 #4 0x080ad128 in m_scheduler () at m_sched.c:459 #5 0x080afa84 in sys_main (argc=1, argv=0x1) at s_main.c:312 #6 0x080b8c0e in main (argc=2, argv=0x2) at s_entry.c:27
cheers ... tim
Yep. That turned out to be a separate bug... thanks.
M
On Thu, Jan 06, 2005 at 08:25:56PM +0100, Tim Blechmann wrote:
hi miller, hi all...
if you have this patch:
key | |atom|
deleting the atom will crash pd:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 8136)] 0x08090581 in atom_string (a=0x8364c18, buf=0xbffff040 "0", bufsize=1000) at m_atom.c:89 89 for (sp = a->a_w.w_symbol->s_name, len = 0, quote = 0; *sp; sp++, len++)(gdb) where #0 0x08090581 in atom_string (a=0x8364c18, buf=0xbffff040 "0", bufsize=1000) at m_atom.c:89 #1 0x080912c8 in binbuf_gettext (x=0x835af50, bufp=0x83602e8, lengthp=0x83602ec) at m_binbuf.c:227 #2 0x08060a9c in rtext_retext (x=0x83602e8) at g_rtext.c:279 #3 0x080594e6 in glist_retext (glist=0x835ad60, y=0x835d8b8) at g_graph.c:142#4 0x0805d3e6 in gatom_redraw (client=0x835d8b8, glist=0x835ad60) at g_text.c:452 #5 0x080993ff in sys_flushqueue () at s_inter.c:736 #6 0x08099476 in sys_poll_togui () at s_inter.c:761 #7 0x080995df in sys_pollgui () at s_inter.c:816 #8 0x080963db in m_scheduler () at m_sched.c:486 #9 0x08096c32 in sys_main (argc=1, argv=0xbffff614) at s_main.c:337 #10 0x0809ceca in main (argc=1, argv=0xbffff614) at s_entry.c:29
the workaround is to delete the connection before deleting the object ... still it's a bug ...
any idea?
cheers ... tim
-- mailto:TimBlechmann@gmx.de ICQ: 96771783 http://www.mokabar.tk
After one look at this planet any visitor from outer space would say "I want to see the manager." William S. Burroughs