Re: [PD] Problems with "pool" object
On Mon, 23 Aug 2010, João Martins wrote: The usual reply to myself kind of thing. I've just tested an earlier pd-extended package, with GEM 0.91.3 (that's the one working in my Mac), and the problem persists. When I create a "pool" instance and open the help patch and then try to close it (this is the fastest way to test, since it produces the same output as putting a fid_class object into the patch), this is what I get at the terminal console: If you can be sure that the problem comes from pool, but the error message doesn't, then you can't rely on the glibc backtrace, nor on a gdb backtrace either. You have to use valgrind, which can do early diagnostic, instead of gdb and glibc that can only tell you the last step of the death. But I don't recall whether it works on OSX, or only Linux. _ _ __ ___ _ _ _ ... | Mathieu Bouchard on the road (in Îles-de-la-Madeleine, QC). ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Problems with "pool" object
On Tue, 24 Aug 2010, Frank Barknecht wrote: I know that one: Isn't it strange that a crash in pool should give an error message about xsample.pd_linux? No. It's a «normal trouble» with C/C++ languages. The solution is to use powerful debuggers that can report mistakes early, by using cpu emulators, very picky code, and implementations of malloc/free that spend a lot of time setting up traps that bugs will have to fall into. That's why I mention valgrind once in a while... someone has to be mentioning it sometimes. _ _ __ ___ _ _ _ ... | Mathieu Bouchard on the road (in Îles-de-la-Madeleine, QC). ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Problems with "pool" object
I'm using the one available at http://g.org/ext/beta/linux/pd/ I'll look into the task of compiling it myself. I use xsample as provided by your site without any problem, and I'm not using flext, just the externals. Here and on my Mac, where everything works just fine. João Martins No dia 24 de Agosto de 2010 18:21, Thomas Grill escreveu: > Hi Joao, > interestingly i haven't asked before: what versions of flext, pool and > xsample are you using? > I'm asking i would always recommend to compile from the svn source - which > should not be all that daunting. I might not be the right source of comfort > but i guess there are people here that can easily lead you through the > process. > gr~~~ > > Am 24.08.2010 um 11:30 schrieb João Martins: > > Nothing is as simple as it looks, as I'm learning by the minute. > With the latest release of Pd, turning off Gem does not allow "pool" to > work properly, and I get exactly the same error message. > This leads me back to "pool" in itself. > Compiling all of "flext" really seems a daunting task, but I think I'll > give it a go, if no one comes up with a better suggestion. ;) > > Thank you all. > > João Martins > > No dia 24 de Agosto de 2010 10:17, João Martins escreveu: > >> So, I've tried using a fresher copy of GEM (0.92.3) and not having xsample >> in the way, and I got apparently the same problem: >> >> *** glibc detected *** pdextended: free(): invalid pointer: 0x09c2b864 *** >> === Backtrace: = >> /lib/tls/i686/cmov/libc.so.6[0x17b0d1] >> /lib/tls/i686/cmov/libc.so.6[0x17c7d2] >> /lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x17f8ad] >> >> /home/user/pd-externals/pool/pool.pd_linux(_ZN17flext_root_singledlEPv+0x32)[0x89d52b4] >> >> /home/user/pd-externals/pool/pool.pd_linux(_ZN12flext_single8AtomList4FreeEv+0x25)[0x89d54d5] >> >> /home/user/pd-externals/pool/pool.pd_linux(_ZN12flext_single8AtomListD1Ev+0x28)[0x89d55a0] >> >> /home/user/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single12AttrDataCont5clearEv+0x60)[0x89d33a6] >> >> /home/abade/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single12AttrDataContD0Ev+0x2a)[0x89d4270] >> >> /home/abade/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single4ExitEv+0x7e)[0x89d0694] >> >> /home/user/pd-externals/pool/pool.pd_linux(_ZN16flext_obj_single8obj_freeEP9flext_hdr+0x7b)[0x89d2021] >> pdextended(pd_free+0x17)[0x80b5af7] >> === Memory map: >> 0011-0024e000 r-xp 08:01 11740506 /lib/tls/i686/cmov/ >> libc-2.10.1.so >> 0024e000-0024f000 ---p 0013e000 08:01 11740506 /lib/tls/i686/cmov/ >> libc-2.10.1.so >> 0024f000-00251000 r--p 0013e000 08:01 11740506 /lib/tls/i686/cmov/ >> libc-2.10.1.so >> 00251000-00252000 rw-p 0014 08:01 11740506 /lib/tls/i686/cmov/ >> libc-2.10.1.so >> 00252000-00255000 rw-p 00:00 0 >> 00255000-00266000 r-xp 08:01 10455586 /usr/lib/libcelt.so.0.0.0 >> 00266000-00267000 r--p 0001 08:01 10455586 /usr/lib/libcelt.so.0.0.0 >> 00267000-00268000 rw-p 00011000 08:01 10455586 /usr/lib/libcelt.so.0.0.0 >> 00268000-0026f000 r-xp 08:01 10454666 /usr/lib/libSM.so.6.0.0 >> 0026f000-0027 r--p 6000 08:01 10454666 /usr/lib/libSM.so.6.0.0 >> 0027-00271000 rw-p 7000 08:01 10454666 /usr/lib/libSM.so.6.0.0 >> 00271000-00274000 r-xp 08:01 11722789 /lib/libuuid.so.1.3.0 >> 00274000-00275000 r--p 2000 08:01 11722789 /lib/libuuid.so.1.3.0 >> 00275000-00276000 rw-p 3000 08:01 11722789 /lib/libuuid.so.1.3.0 >> 00276000-00278000 r-xp 08:01 11740517 /lib/tls/i686/cmov/ >> libdl-2.10.1.so >> 00278000-00279000 r--p 1000 08:01 11740517 /lib/tls/i686/cmov/ >> libdl-2.10.1.so >> 00279000-0027a000 rw-p 2000 08:01 11740517 /lib/tls/i686/cmov/ >> libdl-2.10.1.so >> 0027a000-002c2000 r-xp 08:01 10455789 /usr/lib/ >> libpulsecommon-0.9.19.so >> 002c2000-002c3000 r--p 00047000 08:01 10455789 /usr/lib/ >> libpulsecommon-0.9.19.so >> 002c3000-002c4000 rw-p 00048000 08:01 10455789 /usr/lib/ >> libpulsecommon-0.9.19.so >> 002c4000-002c8000 r-xp 08:01 10455682 /usr/lib/libXtst.so.6.1.0 >> 002c8000-002c9000 r--p 4000 08:01 10455682 /usr/lib/libXtst.so.6.1.0 >> 002c9000-002ca000 rw-p 5000 08:01 10455682 /usr/lib/libXtst.so.6.1.0 >> 002ca000-0033 r-xp 08:01 10455079 >> /usr/lib/libsndfile.so.1.0.20 >> 0033-00331000 r--p 00065000 08:01 10455079 >> /usr/lib/libsndfile.so.1.0.20 >> 00331000-00332000 rw-p 00066000 08:01 10455079 >> /usr/lib/libsndfile.so.1.0.20 >> 00332000-00336000 rw-p 00:00 0 >> 00336000-00344000 r-xp 08:01 10452994 /usr/lib/libXext.so.6.4.0 >> 00344000-00345000 r--p d000 08:01 10452994 /usr/lib/libXext.so.6.4.0 >> 00345000-00346000 rw-p e000 08:01 10452994 /usr/lib/libXext.so.6.4.0 >> 00346000-00359000 r-xp 08:01 11740525 /lib/tls/i686/cmov/ >> libnsl-2.10.1.so >> 00359000-0035a000 r--p 00012000 08:01 11740525 /lib/tls/i686/cmov/ >> libnsl-2.10.1.so >> 0035a000-0035b00
Re: [PD] Problems with "pool" object
Hi Joao, interestingly i haven't asked before: what versions of flext, pool and xsample are you using? I'm asking i would always recommend to compile from the svn source - which should not be all that daunting. I might not be the right source of comfort but i guess there are people here that can easily lead you through the process. gr~~~ Am 24.08.2010 um 11:30 schrieb João Martins: > Nothing is as simple as it looks, as I'm learning by the minute. > With the latest release of Pd, turning off Gem does not allow "pool" to work > properly, and I get exactly the same error message. > This leads me back to "pool" in itself. > Compiling all of "flext" really seems a daunting task, but I think I'll give > it a go, if no one comes up with a better suggestion. ;) > > Thank you all. > > João Martins > > No dia 24 de Agosto de 2010 10:17, João Martins > escreveu: > So, I've tried using a fresher copy of GEM (0.92.3) and not having xsample in > the way, and I got apparently the same problem: > > *** glibc detected *** pdextended: free(): invalid pointer: 0x09c2b864 *** > === Backtrace: = > /lib/tls/i686/cmov/libc.so.6[0x17b0d1] > /lib/tls/i686/cmov/libc.so.6[0x17c7d2] > /lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x17f8ad] > /home/user/pd-externals/pool/pool.pd_linux(_ZN17flext_root_singledlEPv+0x32)[0x89d52b4] > /home/user/pd-externals/pool/pool.pd_linux(_ZN12flext_single8AtomList4FreeEv+0x25)[0x89d54d5] > /home/user/pd-externals/pool/pool.pd_linux(_ZN12flext_single8AtomListD1Ev+0x28)[0x89d55a0] > /home/user/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single12AttrDataCont5clearEv+0x60)[0x89d33a6] > /home/abade/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single12AttrDataContD0Ev+0x2a)[0x89d4270] > /home/abade/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single4ExitEv+0x7e)[0x89d0694] > /home/user/pd-externals/pool/pool.pd_linux(_ZN16flext_obj_single8obj_freeEP9flext_hdr+0x7b)[0x89d2021] > pdextended(pd_free+0x17)[0x80b5af7] > === Memory map: > 0011-0024e000 r-xp 08:01 11740506 > /lib/tls/i686/cmov/libc-2.10.1.so > 0024e000-0024f000 ---p 0013e000 08:01 11740506 > /lib/tls/i686/cmov/libc-2.10.1.so > 0024f000-00251000 r--p 0013e000 08:01 11740506 > /lib/tls/i686/cmov/libc-2.10.1.so > 00251000-00252000 rw-p 0014 08:01 11740506 > /lib/tls/i686/cmov/libc-2.10.1.so > 00252000-00255000 rw-p 00:00 0 > 00255000-00266000 r-xp 08:01 10455586 /usr/lib/libcelt.so.0.0.0 > 00266000-00267000 r--p 0001 08:01 10455586 /usr/lib/libcelt.so.0.0.0 > 00267000-00268000 rw-p 00011000 08:01 10455586 /usr/lib/libcelt.so.0.0.0 > 00268000-0026f000 r-xp 08:01 10454666 /usr/lib/libSM.so.6.0.0 > 0026f000-0027 r--p 6000 08:01 10454666 /usr/lib/libSM.so.6.0.0 > 0027-00271000 rw-p 7000 08:01 10454666 /usr/lib/libSM.so.6.0.0 > 00271000-00274000 r-xp 08:01 11722789 /lib/libuuid.so.1.3.0 > 00274000-00275000 r--p 2000 08:01 11722789 /lib/libuuid.so.1.3.0 > 00275000-00276000 rw-p 3000 08:01 11722789 /lib/libuuid.so.1.3.0 > 00276000-00278000 r-xp 08:01 11740517 > /lib/tls/i686/cmov/libdl-2.10.1.so > 00278000-00279000 r--p 1000 08:01 11740517 > /lib/tls/i686/cmov/libdl-2.10.1.so > 00279000-0027a000 rw-p 2000 08:01 11740517 > /lib/tls/i686/cmov/libdl-2.10.1.so > 0027a000-002c2000 r-xp 08:01 10455789 > /usr/lib/libpulsecommon-0.9.19.so > 002c2000-002c3000 r--p 00047000 08:01 10455789 > /usr/lib/libpulsecommon-0.9.19.so > 002c3000-002c4000 rw-p 00048000 08:01 10455789 > /usr/lib/libpulsecommon-0.9.19.so > 002c4000-002c8000 r-xp 08:01 10455682 /usr/lib/libXtst.so.6.1.0 > 002c8000-002c9000 r--p 4000 08:01 10455682 /usr/lib/libXtst.so.6.1.0 > 002c9000-002ca000 rw-p 5000 08:01 10455682 /usr/lib/libXtst.so.6.1.0 > 002ca000-0033 r-xp 08:01 10455079 /usr/lib/libsndfile.so.1.0.20 > 0033-00331000 r--p 00065000 08:01 10455079 /usr/lib/libsndfile.so.1.0.20 > 00331000-00332000 rw-p 00066000 08:01 10455079 /usr/lib/libsndfile.so.1.0.20 > 00332000-00336000 rw-p 00:00 0 > 00336000-00344000 r-xp 08:01 10452994 /usr/lib/libXext.so.6.4.0 > 00344000-00345000 r--p d000 08:01 10452994 /usr/lib/libXext.so.6.4.0 > 00345000-00346000 rw-p e000 08:01 10452994 /usr/lib/libXext.so.6.4.0 > 00346000-00359000 r-xp 08:01 11740525 > /lib/tls/i686/cmov/libnsl-2.10.1.so > 00359000-0035a000 r--p 00012000 08:01 11740525 > /lib/tls/i686/cmov/libnsl-2.10.1.so > 0035a000-0035b000 rw-p 00013000 08:01 11740525 > /lib/tls/i686/cmov/libnsl-2.10.1.so > 0035b000-0035d000 rw-p 00:00 0 > 0035d000-003ab000 r-xp 08:01 10453276 /usr/lib/libFLAC.so.8.2.0 > 003ab000-003ac000 r--p 0004d000 08:01 10453276 /usr/lib/libFLAC.so.8.2.0 > 003ac000-003ad000 rw-p 0004e000 08:01 10453276 /usr/lib/libFLAC.so.8.2.0 > 003ad000-003b2000 r-xp 08:01 10453274 /usr/lib/libogg.so.0.6.0 > 003b2000-003b3000
Re: [PD] Problems with "pool" object
moin João,
Not that I think this will be of much help, but when I had similar
flext-related crashes ("free(): invalid pointer") in the past, it turned
out to be due to missing initialization code in the constructor. I
really don't believe [pool] suffers from this problem (we would have
heard about it before now), but cf. my signature :-/
Anyhoo, I found it helped (but didn't solve all problems) to compile the
flext externals in "static debug" mode -- of course, this causes some
memory bloat and slows things down a bit, but it might get you running
on your target architecture...
marmosets,
Bryan
On 2010-08-24 11:30:30, João Martins appears to
have written:
> Nothing is as simple as it looks, as I'm learning by the minute.
> With the latest release of Pd, turning off Gem does not allow "pool" to
> work properly, and I get exactly the same error message.
> This leads me back to "pool" in itself.
> Compiling all of "flext" really seems a daunting task, but I think I'll
> give it a go, if no one comes up with a better suggestion. ;)
>
> Thank you all.
>
> João Martins
--
Bryan Jurish "There is *always* one more bug."
jur...@ling.uni-potsdam.de -Lubarsky's Law of Cybernetic Entomology
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Re: [PD] Problems with "pool" object
Nothing is as simple as it looks, as I'm learning by the minute. With the latest release of Pd, turning off Gem does not allow "pool" to work properly, and I get exactly the same error message. This leads me back to "pool" in itself. Compiling all of "flext" really seems a daunting task, but I think I'll give it a go, if no one comes up with a better suggestion. ;) Thank you all. João Martins No dia 24 de Agosto de 2010 10:17, João Martins escreveu: > So, I've tried using a fresher copy of GEM (0.92.3) and not having xsample > in the way, and I got apparently the same problem: > > *** glibc detected *** pdextended: free(): invalid pointer: 0x09c2b864 *** > === Backtrace: = > /lib/tls/i686/cmov/libc.so.6[0x17b0d1] > /lib/tls/i686/cmov/libc.so.6[0x17c7d2] > /lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x17f8ad] > > /home/user/pd-externals/pool/pool.pd_linux(_ZN17flext_root_singledlEPv+0x32)[0x89d52b4] > > /home/user/pd-externals/pool/pool.pd_linux(_ZN12flext_single8AtomList4FreeEv+0x25)[0x89d54d5] > > /home/user/pd-externals/pool/pool.pd_linux(_ZN12flext_single8AtomListD1Ev+0x28)[0x89d55a0] > > /home/user/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single12AttrDataCont5clearEv+0x60)[0x89d33a6] > > /home/abade/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single12AttrDataContD0Ev+0x2a)[0x89d4270] > > /home/abade/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single4ExitEv+0x7e)[0x89d0694] > > /home/user/pd-externals/pool/pool.pd_linux(_ZN16flext_obj_single8obj_freeEP9flext_hdr+0x7b)[0x89d2021] > pdextended(pd_free+0x17)[0x80b5af7] > === Memory map: > 0011-0024e000 r-xp 08:01 11740506 /lib/tls/i686/cmov/ > libc-2.10.1.so > 0024e000-0024f000 ---p 0013e000 08:01 11740506 /lib/tls/i686/cmov/ > libc-2.10.1.so > 0024f000-00251000 r--p 0013e000 08:01 11740506 /lib/tls/i686/cmov/ > libc-2.10.1.so > 00251000-00252000 rw-p 0014 08:01 11740506 /lib/tls/i686/cmov/ > libc-2.10.1.so > 00252000-00255000 rw-p 00:00 0 > 00255000-00266000 r-xp 08:01 10455586 /usr/lib/libcelt.so.0.0.0 > 00266000-00267000 r--p 0001 08:01 10455586 /usr/lib/libcelt.so.0.0.0 > 00267000-00268000 rw-p 00011000 08:01 10455586 /usr/lib/libcelt.so.0.0.0 > 00268000-0026f000 r-xp 08:01 10454666 /usr/lib/libSM.so.6.0.0 > 0026f000-0027 r--p 6000 08:01 10454666 /usr/lib/libSM.so.6.0.0 > 0027-00271000 rw-p 7000 08:01 10454666 /usr/lib/libSM.so.6.0.0 > 00271000-00274000 r-xp 08:01 11722789 /lib/libuuid.so.1.3.0 > 00274000-00275000 r--p 2000 08:01 11722789 /lib/libuuid.so.1.3.0 > 00275000-00276000 rw-p 3000 08:01 11722789 /lib/libuuid.so.1.3.0 > 00276000-00278000 r-xp 08:01 11740517 /lib/tls/i686/cmov/ > libdl-2.10.1.so > 00278000-00279000 r--p 1000 08:01 11740517 /lib/tls/i686/cmov/ > libdl-2.10.1.so > 00279000-0027a000 rw-p 2000 08:01 11740517 /lib/tls/i686/cmov/ > libdl-2.10.1.so > 0027a000-002c2000 r-xp 08:01 10455789 /usr/lib/ > libpulsecommon-0.9.19.so > 002c2000-002c3000 r--p 00047000 08:01 10455789 /usr/lib/ > libpulsecommon-0.9.19.so > 002c3000-002c4000 rw-p 00048000 08:01 10455789 /usr/lib/ > libpulsecommon-0.9.19.so > 002c4000-002c8000 r-xp 08:01 10455682 /usr/lib/libXtst.so.6.1.0 > 002c8000-002c9000 r--p 4000 08:01 10455682 /usr/lib/libXtst.so.6.1.0 > 002c9000-002ca000 rw-p 5000 08:01 10455682 /usr/lib/libXtst.so.6.1.0 > 002ca000-0033 r-xp 08:01 10455079 > /usr/lib/libsndfile.so.1.0.20 > 0033-00331000 r--p 00065000 08:01 10455079 > /usr/lib/libsndfile.so.1.0.20 > 00331000-00332000 rw-p 00066000 08:01 10455079 > /usr/lib/libsndfile.so.1.0.20 > 00332000-00336000 rw-p 00:00 0 > 00336000-00344000 r-xp 08:01 10452994 /usr/lib/libXext.so.6.4.0 > 00344000-00345000 r--p d000 08:01 10452994 /usr/lib/libXext.so.6.4.0 > 00345000-00346000 rw-p e000 08:01 10452994 /usr/lib/libXext.so.6.4.0 > 00346000-00359000 r-xp 08:01 11740525 /lib/tls/i686/cmov/ > libnsl-2.10.1.so > 00359000-0035a000 r--p 00012000 08:01 11740525 /lib/tls/i686/cmov/ > libnsl-2.10.1.so > 0035a000-0035b000 rw-p 00013000 08:01 11740525 /lib/tls/i686/cmov/ > libnsl-2.10.1.so > 0035b000-0035d000 rw-p 00:00 0 > 0035d000-003ab000 r-xp 08:01 10453276 /usr/lib/libFLAC.so.8.2.0 > 003ab000-003ac000 r--p 0004d000 08:01 10453276 /usr/lib/libFLAC.so.8.2.0 > 003ac000-003ad000 rw-p 0004e000 08:01 10453276 /usr/lib/libFLAC.so.8.2.0 > 003ad000-003b2000 r-xp 08:01 10453274 /usr/lib/libogg.so.0.6.0 > 003b2000-003b3000 r--p 4000 08:01 10453274 /usr/lib/libogg.so.0.6.0 > 003b3000-003b4000 rw-p 5000 08:01 10453274 /usr/lib/libogg.so.0.6.0 > 003b4000-003b8000 r-xp 08:01 10455652 /usr/lib/libXdmcp.so.6.0.0 > 003b8000-003b9000 rw-p 3000 08:01 10455652 /usr/lib/libXdmcp.so.6.0.0 > 003b9000-003bb000 r-xp 08:01 10455664 > /usr/lib/libXinerama.so.1.0.0 > 003bb000-003bc000 rw-p 1000 08:01
Re: [PD] Problems with "pool" object
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/24/2010 11:17 AM, João Martins wrote: > So, I've tried using a fresher copy of GEM (0.92.3) and not having xsample > in the way, and I got apparently the same problem: oops, i just checked the 0.92 sources, and it seems that my fix is not there yet. if you feel experimental, you could try to build Gem from svn/trunk and see whether it works then. if not then probably the same measurements (protecting new/delete) have to be taken on the flext side as well, but i don't know the code there... > > *** glibc detected *** pdextended: free(): invalid pointer: 0x09c2b864 *** "free()" indicates that i might have guessed the problem right... fgasdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxzkHcACgkQkX2Xpv6ydvRzuQCg2smjBIjZ7WO32SayCmIFYb59 3vMAni+9RwJzHg7/yp9dZJzIvv9CBk0d =5QR0 -END PGP SIGNATURE- ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Problems with "pool" object
So, I've tried using a fresher copy of GEM (0.92.3) and not having xsample in the way, and I got apparently the same problem: *** glibc detected *** pdextended: free(): invalid pointer: 0x09c2b864 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0x17b0d1] /lib/tls/i686/cmov/libc.so.6[0x17c7d2] /lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x17f8ad] /home/user/pd-externals/pool/pool.pd_linux(_ZN17flext_root_singledlEPv+0x32)[0x89d52b4] /home/user/pd-externals/pool/pool.pd_linux(_ZN12flext_single8AtomList4FreeEv+0x25)[0x89d54d5] /home/user/pd-externals/pool/pool.pd_linux(_ZN12flext_single8AtomListD1Ev+0x28)[0x89d55a0] /home/user/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single12AttrDataCont5clearEv+0x60)[0x89d33a6] /home/abade/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single12AttrDataContD0Ev+0x2a)[0x89d4270] /home/abade/pd-externals/pool/pool.pd_linux(_ZN17flext_base_single4ExitEv+0x7e)[0x89d0694] /home/user/pd-externals/pool/pool.pd_linux(_ZN16flext_obj_single8obj_freeEP9flext_hdr+0x7b)[0x89d2021] pdextended(pd_free+0x17)[0x80b5af7] === Memory map: 0011-0024e000 r-xp 08:01 11740506 /lib/tls/i686/cmov/ libc-2.10.1.so 0024e000-0024f000 ---p 0013e000 08:01 11740506 /lib/tls/i686/cmov/ libc-2.10.1.so 0024f000-00251000 r--p 0013e000 08:01 11740506 /lib/tls/i686/cmov/ libc-2.10.1.so 00251000-00252000 rw-p 0014 08:01 11740506 /lib/tls/i686/cmov/ libc-2.10.1.so 00252000-00255000 rw-p 00:00 0 00255000-00266000 r-xp 08:01 10455586 /usr/lib/libcelt.so.0.0.0 00266000-00267000 r--p 0001 08:01 10455586 /usr/lib/libcelt.so.0.0.0 00267000-00268000 rw-p 00011000 08:01 10455586 /usr/lib/libcelt.so.0.0.0 00268000-0026f000 r-xp 08:01 10454666 /usr/lib/libSM.so.6.0.0 0026f000-0027 r--p 6000 08:01 10454666 /usr/lib/libSM.so.6.0.0 0027-00271000 rw-p 7000 08:01 10454666 /usr/lib/libSM.so.6.0.0 00271000-00274000 r-xp 08:01 11722789 /lib/libuuid.so.1.3.0 00274000-00275000 r--p 2000 08:01 11722789 /lib/libuuid.so.1.3.0 00275000-00276000 rw-p 3000 08:01 11722789 /lib/libuuid.so.1.3.0 00276000-00278000 r-xp 08:01 11740517 /lib/tls/i686/cmov/ libdl-2.10.1.so 00278000-00279000 r--p 1000 08:01 11740517 /lib/tls/i686/cmov/ libdl-2.10.1.so 00279000-0027a000 rw-p 2000 08:01 11740517 /lib/tls/i686/cmov/ libdl-2.10.1.so 0027a000-002c2000 r-xp 08:01 10455789 /usr/lib/ libpulsecommon-0.9.19.so 002c2000-002c3000 r--p 00047000 08:01 10455789 /usr/lib/ libpulsecommon-0.9.19.so 002c3000-002c4000 rw-p 00048000 08:01 10455789 /usr/lib/ libpulsecommon-0.9.19.so 002c4000-002c8000 r-xp 08:01 10455682 /usr/lib/libXtst.so.6.1.0 002c8000-002c9000 r--p 4000 08:01 10455682 /usr/lib/libXtst.so.6.1.0 002c9000-002ca000 rw-p 5000 08:01 10455682 /usr/lib/libXtst.so.6.1.0 002ca000-0033 r-xp 08:01 10455079 /usr/lib/libsndfile.so.1.0.20 0033-00331000 r--p 00065000 08:01 10455079 /usr/lib/libsndfile.so.1.0.20 00331000-00332000 rw-p 00066000 08:01 10455079 /usr/lib/libsndfile.so.1.0.20 00332000-00336000 rw-p 00:00 0 00336000-00344000 r-xp 08:01 10452994 /usr/lib/libXext.so.6.4.0 00344000-00345000 r--p d000 08:01 10452994 /usr/lib/libXext.so.6.4.0 00345000-00346000 rw-p e000 08:01 10452994 /usr/lib/libXext.so.6.4.0 00346000-00359000 r-xp 08:01 11740525 /lib/tls/i686/cmov/ libnsl-2.10.1.so 00359000-0035a000 r--p 00012000 08:01 11740525 /lib/tls/i686/cmov/ libnsl-2.10.1.so 0035a000-0035b000 rw-p 00013000 08:01 11740525 /lib/tls/i686/cmov/ libnsl-2.10.1.so 0035b000-0035d000 rw-p 00:00 0 0035d000-003ab000 r-xp 08:01 10453276 /usr/lib/libFLAC.so.8.2.0 003ab000-003ac000 r--p 0004d000 08:01 10453276 /usr/lib/libFLAC.so.8.2.0 003ac000-003ad000 rw-p 0004e000 08:01 10453276 /usr/lib/libFLAC.so.8.2.0 003ad000-003b2000 r-xp 08:01 10453274 /usr/lib/libogg.so.0.6.0 003b2000-003b3000 r--p 4000 08:01 10453274 /usr/lib/libogg.so.0.6.0 003b3000-003b4000 rw-p 5000 08:01 10453274 /usr/lib/libogg.so.0.6.0 003b4000-003b8000 r-xp 08:01 10455652 /usr/lib/libXdmcp.so.6.0.0 003b8000-003b9000 rw-p 3000 08:01 10455652 /usr/lib/libXdmcp.so.6.0.0 003b9000-003bb000 r-xp 08:01 10455664 /usr/lib/libXinerama.so.1.0.0 003bb000-003bc000 rw-p 1000 08:01 10455664 /usr/lib/libXinerama.so.1.0.0 003bc000-003bd000 r-xp 08:01 10527044 /usr/lib/tls/libnvidia-tls.so.185.18.36 003bd000-003be000 rw-p 08:01 10527044 /usr/lib/tls/libnvidia-tls.so.185.18.36 003be000-003d3000 r-xp 08:01 11740583 /lib/tls/i686/cmov/ libpthread-2.10.1.so 003d3000-003d4000 r--p 00014000 08:01 11740583 /lib/tls/i686/cmov/ libpthread-2.10.1.so 003d4000-003d5000 rw-p 00015000 08:01 11740583 /lib/tls/i686/cmov/ libpthread-2.10.1.so 003d5000-003d7000 rw-p 00:00 0 003d7000-00541000 r-xp 08:01 10453340 /usr/lib/libsamplerate.so.0.1.7 00541000-00542000 r--p 00
Re: [PD] Problems with "pool" object
On Tue, Aug 24, 2010 at 09:33:53AM +0100, João Martins wrote: > Well... I'll test to see if it is really a problem between pool and xsample > (they both work on my Mac), and not GEM. Did you notice that if I take Gem > out, pool and xsample stop having problems? Ah, no, I overlooked that. Then I would rather get a fresh Gem first, it may be available in one of the newer Pd-extended versions. > But I'm more than willing to follow any suggestions. Could I ask you for > instructions on how to "recompile everything related to flext with the > newest versions of the sources"? Or a good link for Linux newbies? Puh, it's been a while since I compiled it. http://puredata.info/Members/thomas/flext should have the most current information. Ciao -- Frank ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Problems with "pool" object
Well... I'll test to see if it is really a problem between pool and xsample (they both work on my Mac), and not GEM. Did you notice that if I take Gem out, pool and xsample stop having problems? But I'm more than willing to follow any suggestions. Could I ask you for instructions on how to "recompile everything related to flext with the newest versions of the sources"? Or a good link for Linux newbies? Thanks. João Martins 2010/8/24 Frank Barknecht > On Mon, Aug 23, 2010 at 08:47:24PM +0100, João Martins wrote: > > When I create a "pool" instance and open the help patch and then try to > > close it (this is the fastest way to test, since it produces the same > output > > as putting a fid_class object into the patch), this is what I get at the > > terminal console: > > > > *** glibc detected *** pd: free(): invalid pointer: 0x0a53dd2c *** > > === Backtrace: = > > /lib/tls/i686/cmov/libc.so.6[0xb7515704] > > /lib/tls/i686/cmov/libc.so.6(cfree+0x96)[0xb75176b6] > > > /home/user/pd-externals/xsample/xsample.pd_linux(_ZN17flext_root_singledlEPv+0x32)[0xb5b337b4] > > > /home/user/pd-externals/xsample/xsample.pd_linux(_ZN12flext_single8AtomList4FreeEv+0x25)[0xb5b33975] > > I know that one: Isn't it strange that a crash in pool should give an > error message about xsample.pd_linux? I don't know the exact reason for > this, but a quick fix was to remove xsample.pd_linux when using pool. Of > course then you cannot use xsample. :( > > So the less quick fix for me was to recompile everything related to > flext with the newest versions of the sources. > > Ciao > -- > Frank > > ___ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > -- João Pedro Martins música . web design http://joaomartins.entropiadesign.org mail: joaomart...@mac.com skype: joaopsmartins ichat: joaomartins msn: joaopsmartins ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Problems with "pool" object
On Mon, Aug 23, 2010 at 08:47:24PM +0100, João Martins wrote: > When I create a "pool" instance and open the help patch and then try to > close it (this is the fastest way to test, since it produces the same output > as putting a fid_class object into the patch), this is what I get at the > terminal console: > > *** glibc detected *** pd: free(): invalid pointer: 0x0a53dd2c *** > === Backtrace: = > /lib/tls/i686/cmov/libc.so.6[0xb7515704] > /lib/tls/i686/cmov/libc.so.6(cfree+0x96)[0xb75176b6] > /home/user/pd-externals/xsample/xsample.pd_linux(_ZN17flext_root_singledlEPv+0x32)[0xb5b337b4] > /home/user/pd-externals/xsample/xsample.pd_linux(_ZN12flext_single8AtomList4FreeEv+0x25)[0xb5b33975] I know that one: Isn't it strange that a crash in pool should give an error message about xsample.pd_linux? I don't know the exact reason for this, but a quick fix was to remove xsample.pd_linux when using pool. Of course then you cannot use xsample. :( So the less quick fix for me was to recompile everything related to flext with the newest versions of the sources. Ciao -- Frank ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Problems with "pool" object
The usual reply to myself kind of thing. I've just tested an earlier pd-extended package, with GEM 0.91.3 (that's the one working in my Mac), and the problem persists. When I create a "pool" instance and open the help patch and then try to close it (this is the fastest way to test, since it produces the same output as putting a fid_class object into the patch), this is what I get at the terminal console: *** glibc detected *** pd: free(): invalid pointer: 0x0a53dd2c *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0xb7515704] /lib/tls/i686/cmov/libc.so.6(cfree+0x96)[0xb75176b6] /home/user/pd-externals/xsample/xsample.pd_linux(_ZN17flext_root_singledlEPv+0x32)[0xb5b337b4] /home/user/pd-externals/xsample/xsample.pd_linux(_ZN12flext_single8AtomList4FreeEv+0x25)[0xb5b33975] /home/user/pd-externals/xsample/xsample.pd_linux(_ZN12flext_single8AtomListD1Ev+0x28)[0xb5b33a40] /home/user/pd-externals/xsample/xsample.pd_linux(_ZN17flext_base_single12AttrDataCont5clearEv+0x60)[0xb5b318a6] /home/user/pd-externals/xsample/xsample.pd_linux(_ZN17flext_base_single12AttrDataContD0Ev+0x2a)[0xb5b32770] /home/user/pd-externals/xsample/xsample.pd_linux(_ZN17flext_base_single4ExitEv+0x7e)[0xb5b2dfa4] /home/user/pd-externals/xsample/xsample.pd_linux(_ZN16flext_obj_single8obj_freeEP9flext_hdr+0x7b)[0xb5b30521] pd(pd_free+0x17)[0x80b67e7] === Memory map: 08048000-08111000 r-xp 08:01 10455173 /usr/bin/pd 08111000-08112000 r--p 000c8000 08:01 10455173 /usr/bin/pd 08112000-08113000 rw-p 000c9000 08:01 10455173 /usr/bin/pd 08113000-0852 rw-p 08113000 00:00 0 0a4b6000-0a543000 rw-p 0a4b6000 00:00 0 [heap] b560-b5621000 rw-p b560 00:00 0 b5621000-b570 ---p b5621000 00:00 0 b576c000-b57eb000 rw-p b6622000 00:00 0 b582c000-b5865000 r-xp 08:01 7029267 /home/user/pd-externals/pool/pool.pd_linux b5865000-b5866000 r--p 00038000 08:01 7029267 /home/user/pd-externals/pool/pool.pd_linux b5866000-b5867000 rw-p 00039000 08:01 7029267 /home/user/pd-externals/pool/pool.pd_linux b5867000-b5868000 rw-p b5867000 00:00 0 b5868000-b5879000 r--p 08:01 10594421 /usr/share/fonts/truetype/ttf-bitstream-vera/Vera.ttf b5879000-b58c9000 r-xp 08:01 10455130 /usr/lib/libImlib2.so.1.4.2 b58c9000-b58ca000 r--p 0004f000 08:01 10455130 /usr/lib/libImlib2.so.1.4.2 b58ca000-b58cb000 rw-p 0005 08:01 10455130 /usr/lib/libImlib2.so.1.4.2 b58cb000-b58df000 rw-p b58cb000 00:00 0 b58df000-b5921000 r-xp 08:01 10455140 /usr/lib/libmp3lame.so.0.0.0 b5921000-b5922000 r--p 00042000 08:01 10455140 /usr/lib/libmp3lame.so.0.0.0 b5922000-b5924000 rw-p 00043000 08:01 10455140 /usr/lib/libmp3lame.so.0.0.0 b5924000-b5954000 rw-p b5924000 00:00 0 b5954000-b595f000 r-xp 08:01 10455079 /usr/lib/libvorbisenc.so.2.0.3 b595f000-b596 r--p a000 08:01 10455079 /usr/lib/libvorbisenc.so.2.0.3 b596-b5a5 rw-p b000 08:01 10455079 /usr/lib/libvorbisenc.so.2.0.3 b5a5-b5a6b000 r-xp 08:01 10455076 /usr/lib/libvorbis.so.0.4.0 b5a6b000-b5a6c000 r--p 0001a000 08:01 10455076 /usr/lib/libvorbis.so.0.4.0 b5a6c000-b5a7a000 rw-p 0001b000 08:01 10455076 /usr/lib/libvorbis.so.0.4.0 b5a7a000-b5a7e000 r-xp 08:01 10456342 /usr/lib/libogg.so.0.5.3 b5a7e000-b5a7f000 r--p 3000 08:01 10456342 /usr/lib/libogg.so.0.5.3 b5a7f000-b5a8 rw-p 4000 08:01 10456342 /usr/lib/libogg.so.0.5.3 b5a8-b5acf000 r-xp 08:01 10456539 /usr/lib/libtheora.so.0.3.4 b5acf000-b5ad r--p 0004e000 08:01 10456539 /usr/lib/libtheora.so.0.3.4 b5ad-b5ad1000 rw-p 0004f000 08:01 10456539 /usr/lib/libtheora.so.0.3.4 b5b1-b5b47000 r-xp 08:01 7029270 /home/user/pd-externals/xsample/xsample.pd_linux b5b47000-b5b48000 ---p 00037000 08:01 7029270 /home/user/pd-externals/xsample/xsample.pd_linux b5b48000-b5b49000 r--p 00037000 08:01 7029270 /home/user/pd-externals/xsample/xsample.pd_linux b5b49000-b5b4a000 rw-p 00038000 08:01 7029270 /home/abade/pd-externals/xsample/xsample.pd_linux b5b4a000-b5b4c000 rw-p b5b4a000 00:00 0 b5b4c000-b5b4d000 ---p b5b4c000 00:00 0 b5b4d000-b634d000 rwxp b5b4d000 00:00 0 b634d000-b6371000 r-xp 08:01 10454683 /usr/lib/libpng12.so.0.27.0 b6371000-b6372000 r--p 00023000 08:01 10454683 /usr/lib/libpng12.so.0.27.0 b6372000-b6373000 rw-p 00024000 08:01 10454683 /usr/lib/libpng12.so.0.27.0 b6373000-b654a000Pd: signal 6 It's exactly the same kind of problem I had with the latest builds of Pd-extended. So... is it a Linux thing? The Pd console doesn't produce any output and it just gets "freezed" and I have to shut it down via terminal. I've tested it once with a real time kernel and the -rt flag, and I got the repetition of the "watchdog" process, but nothing else. When I tested "Pd-vanilla" I've noticed, as did other users, that GEM warns about replacements on file or command names. Could that be responsible for these problems I'm experiencing? Any help will be appreciated. João Martins No dia 23
[PD] Problems with "pool" object
Greetings. This is my first mail sent to the pd-list, that I've used often as a resource to solve my Pd problems. Thomas Grill, the author of "pool" and all the other "flext" goodness, such as the xsample externals recommended asking help here, since the problem I'm facing is somewhat specific. I use Pd-extended 0.41.4 on my MacBook as my main programming environment and I'm developing an installation project that uses a tangible interface and fiducials. For better tracking and management of the fiducials, I'm using JY Gratius' abstractions, that require "pool". No problem on my Mac, but the deployment of the installation has to be done with a Linux machine, and now I'm facing some strange issues. The available Pd-extended packages for recent Linux distributions are 0.42.5-rc5 and they seem to work just fine (I'm trying out Ubuntu and Ubuntu Studio 9.10 and 10.04), but whenever I try to use the pool object (directly, or via the fid_class object from fid_abs), PureData freezes. I've launch it via terminal with the double verbose option and I get a lot of jibberish (I'm really a newbie when it comes to Linux) and some of the error I got point in the direction of Gem. Some even pointed to early discussions here about Gem versions and flext externals and problems with file or command name replacements (sorry but I can't find the link, now...). I've made a simple test, following one of Grill's suggestions here on the mailing list of testing on Pd-vanilla, and the fact is that when I disable GEM, "pool" works just fine. But I need GEM and pool working together, as they do on my Mac. Is this a version problem? Does the new Gem "breaks" "pool" and/or other flext objects? Is it a Linux issue? Can anyone point me at the right direction when it comes to having a stable Pd-extended on Linux with externals such as "pool"? Thank you all. João Martins trying to use JY Gratius fid_abs: http://jy.gratius.free.fr/ Thomas Grill pool: http://puredata.info/Members/thomas/pool -- João Pedro Martins música . web design http://joaomartins.entropiadesign.org mail: joaomart...@mac.com skype: joaopsmartins ichat: joaomartins msn: joaopsmartins ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
