Hi Gerda, can you post a simple patch using pool where this is happening? Please include detailed instructions how to reproduce the crash.
thanks, Thomas
Am 13.12.2005 um 16:05 schrieb Gerda Strobl:
Dear list, this is the output from using gdb:
(gdb) run Starting program: /usr/local/bin/pd [Thread debugging using libthread_db enabled] [New Thread -1210120512 (LWP 8469)] *** glibc detected *** double free or corruption (fasttop): 0x0816e808
Program received signal SIGABRT, Aborted. [Switching to Thread -1210120512 (LWP 8469)] 0xb7e1a9e7 in raise () from /lib/tls/libc.so.6 (gdb) where #0 0xb7e1a9e7 in raise () from /lib/tls/libc.so.6 #1 0xb7e1c31b in abort () from /lib/tls/libc.so.6 #2 0xb7e51365 in __fsetlocking () from /lib/tls/libc.so.6 #3 0xb7e57a07 in malloc_usable_size () from /lib/tls/libc.so.6 #4 0xb7e57ea2 in free () from /lib/tls/libc.so.6 #5 0xb7ddd69c in flext_root_single::operator delete () from /usr/local/lib/pd/extra/pool.pd_linux #6 0xb7dd6386 in pooldir::Clear () from /usr/local/lib/pd/extra/pool.pd_linux #7 0xb7dd61db in pooldir::Reset () from /usr/local/lib/pd/extra/pool.pd_linux #8 0xb7dd62a4 in pooldir::~pooldir () from /usr/local/lib/pd/extra/pool.pd_linux #9 0xb7dd637e in pooldir::Clear () from /usr/local/lib/pd/extra/pool.pd_linux #10 0xb7dd61db in pooldir::Reset () from /usr/local/lib/pd/extra/pool.pd_linux #11 0xb7dd62a4 in pooldir::~pooldir () from /usr/local/lib/pd/extra/pool.pd_linux #12 0xb7dd40e0 in pooldata::~pooldata () from /usr/local/lib/pd/extra/pool.pd_linux #13 0xb7dcd7e2 in pool::RmvPool () from /usr/local/lib/pd/extra/pool.pd_linux #14 0xb7dcdb41 in pool::FreePool () from /usr/local/lib/pd/extra/pool.pd_linux #15 0xb7dcf2e2 in pool::~pool () from /usr/local/lib/pd/extra/pool.pd_linux #16 0xb7dd3228 in pool::__free__ () from /usr/local/lib/pd/extra/pool.pd_linux #17 0xb7dd9fd3 in flext_obj_single::obj_free () from /usr/local/lib/pd/extra/pool.pd_linux #18 0x0809f7e7 in pd_free (x=0x8178810) at m_pd.c:33 #19 0x08057709 in glist_delete (x=0x81784c8, y=0x8178810) at g_graph.c:120 #20 0x0805c83c in graph_delete (z=0x81784c8, glist=0x0) at g_graph.c:988 #21 0x08081d6e in gobj_delete (x=0x2115, glist=0x0) at g_editor.c:61 #22 0x080576bd in glist_delete (x=0x81622f8, y=0x81784c8) at g_graph.c:108 #23 0x0805c83c in graph_delete (z=0x81622f8, glist=0x0) at g_graph.c:988 #24 0x08081d6e in gobj_delete (x=0x2115, glist=0x0) at g_editor.c:61 #25 0x080576bd in glist_delete (x=0x81614e0, y=0x81622f8) at g_graph.c:108 #26 0x0805c83c in graph_delete (z=0x81614e0, glist=0x0) at g_graph.c:988 #27 0x08081d6e in gobj_delete (x=0x2115, glist=0x0) at g_editor.c:61 #28 0x080576bd in glist_delete (x=0x81612f0, y=0x81614e0) at g_graph.c:108 #29 0x08054a9c in canvas_free (x=0x81612f0) at g_canvas.c:875 #30 0x0809f7e7 in pd_free (x=0x81612f0) at m_pd.c:33 #31 0x080a094d in pd_typedmess (x=0x81612f0, s=0x2115, argc=135664368, argv=0x3f800000) at m_class.c:728 #32 0x080a0816 in pd_typedmess (x=0x816c3c8, s=0x2115, argc=1, argv=0x80f92a8) at m_class.c:749 #33 0x080a3cf4 in binbuf_eval (x=0x0, target=0x816c3c8, argc=0, argv=0x0) at m_binbuf.c:574 #34 0x080ac130 in socketreceiver_read (x=0x81144c8, fd=0) at s_inter.c:540 #35 0x080adcff in sys_domicrosleep (microsec=0, pollem=1) at s_inter.c:180 #36 0x080ad398 in sys_microsleep (microsec=0) at s_inter.c:202 #37 0x080a8b2f in m_scheduler () at m_sched.c:487 #38 0x080b351b in main (argc=0, argv=0x0) at s_entry.c:27 (gdb) quit The program is running. Exit anyway? (y or n) y socket receive error: Connection reset by peer (104)
lg Gerda Mathieu Bouchard wrote:
On Tue, 13 Dec 2005, Gerda Strobl wrote:
Johannes Burström wrote: http://lists.puredata.info/pipermail/pd-list/2005-11/032513.html that he managed his problem with downgrading the libc6---do I actually have the same problem- should i also downgrade libc6 now?
I'd rather have you post a backtrace. This will enable to fix the bug instead of just pretending that it doesn't exist.
Start Pd using the gdb program by prefixing your commandline with
gdb --args
and then type the "run" command. When the crash happens, use the "where" command to find out how the crash happened. Post the report here. to leave gdb, use "quit" or Ctrl+D; if you do Ctrl+C it won't work because that's reserved for aborting the program that gdb is running.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list