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