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
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
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
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
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
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]
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
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
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
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
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
11 matches
Mail list logo
