very strange. I'm using the latest stable 0.42 in XP. I also tried the
newest .43 build, and doesn't work as well.
Since this is for someone who is only in windows, I won't try it in linux.
2011/11/10 João Pais
this works, but only if I give a complete path, not a relative one. I
can
get
Le 2011-11-11 à 19:52:00, tim vets a écrit :
the 'where' output remains the same afaict...
Well, you're lucky, because it crashes really quickly after the bug :
#7 0xb42514da in freenect_init () from /usr/local/lib/libfreenect.so.0.0
#8 0xb43824cf in fux_kinect::fux_kinect (this=0x8612638,
Le 2011-11-12 à 11:53:00, Mathieu Bouchard a écrit :
But a better fix might be to not use malloc at all for those things, unless
there's a good reason to use it. Less opportunities for bugs.
also, new/delete makes it unnecessary to force pointer casting, and if you
don't try to force it, then
Le 2011-11-11 à 20:05:00, tim vets a écrit :
to my embarrassment I notice that I didn't even change the first lines:
# change to your local directories!
PD_APP_DIR = /Applications/Pd-extended.app/Contents/Resources
PD_DIR =
/Users/xcorex/Documents/Documents/Projects/Puredata/PdSource/Pd-0.42.5-
Le 2011-11-11 à 15:25:00, Hans-Christoph Steiner a écrit :
What has a conflict with libfreenect? I am pretty sure that fux_kinect
uses libfreenect. Is the version in Ubuntu too old? That's a
possibility.
In all likelihood, the memory corruption problem comes from [fux_kinect]
even though
On 12/11/11 16:53, Mathieu Bouchard wrote:
gl_frame_cond = (pthread_cond_t*) malloc(sizeof(pthread_mutex_t));
A nice idiom for malloc is to use the sizeof of the target of the
pointer to which you are assigning its result (no explicit cast needed
when assigning from a void * afaik, at least n
Le 2011-11-11 à 21:54:00, tim vets a écrit :
hey, this is strange, when I run 'valgrind pdextended' and then create
[fux_kinect] it doesn't hang, but just says:
[fux_kinect]: kinect initiated
[fux_kinect]: Number of devices found: 0
[fux_kinect]: Could not open device
The valgrind log (in the
2011/11/12 Mathieu Bouchard
> Le 2011-11-11 à 21:54:00, tim vets a écrit :
>
>
> hey, this is strange, when I run 'valgrind pdextended' and then create
>> [fux_kinect] it doesn't hang, but just says:
>> [fux_kinect]: kinect initiated
>> [fux_kinect]: Number of devices found: 0
>> [fux_kinect]: C
Le 2011-11-12 à 17:13:00, Claude Heiland-Allen a écrit :
A nice idiom for malloc is to use the sizeof of the target of the
pointer to which you are assigning its result (no explicit cast needed
when assigning from a void * afaik, at least no warnings/errors here
with gcc (Debian 4.4.5-8) 4.4.5
Le 2011-11-12 à 18:19:00, tim vets a écrit :
Whenever you have a crash while doing malloc/new, hunt down the Invalid Writes
that you see and it will usually fix the problem.
If it doesn't fix the problem, then it's because there are other Invalid Writes
that valgrind couldn't detect.
indeed, w
2011/11/12 Mathieu Bouchard
> Le 2011-11-12 à 18:19:00, tim vets a écrit :
>
>
> Whenever you have a crash while doing malloc/new, hunt down the Invalid
>> Writes that you see and it will usually fix the problem.
>> If it doesn't fix the problem, then it's because there are other Invalid
>> Writ
2011/11/12 tim vets
>
>
> 2011/11/12 Mathieu Bouchard
>
>> Le 2011-11-12 à 18:19:00, tim vets a écrit :
>>
>>
>> Whenever you have a crash while doing malloc/new, hunt down the Invalid
>>> Writes that you see and it will usually fix the problem.
>>> If it doesn't fix the problem, then it's beca
Le 2011-11-12 à 18:56:00, tim vets a écrit :
it's stretching my knowledge quite far now,
but gave it a shot anyway, and interpreted what you wrote as:
find the line " gl_frame_cond = (pthread_cond_t)
malloc(sizeof(pthread_mutex_t));"
(in fux_kinect.cpp)
and remove the "*" from that line.
Ok,
2011/11/12 Mathieu Bouchard
> Le 2011-11-12 à 18:56:00, tim vets a écrit :
>
>
> it's stretching my knowledge quite far now,
>> but gave it a shot anyway, and interpreted what you wrote as:
>> find the line " gl_frame_cond = (pthread_cond_t)
>> malloc(sizeof(pthread_mutex_t)**);"
>> (in fux_kine
btw, I haven't seen any of the three funders (Andy, Jonathan, Marvin) say
whether their money is just for [expr], or does it include [expr~] and/or
[fexpr~] as well. The task description should be made clearer.
Also, there's no webpage about it. Perhaps you could get together to write
a page
Le 2011-11-10 à 08:46:00, Jonathan Wilkes a écrit :
- Original Message -
From: Mathieu Bouchard
(this doesn't
take ~-objects into account, who use a different execution model)
breadth-first?
No. Breadth-first (queueing) is the execution model of t_clock components,
which are cen
On Sat, Nov 12, 2011 at 03:24:27PM -0500, Mathieu Bouchard wrote:
> btw, I haven't seen any of the three funders (Andy, Jonathan, Marvin) say
> whether their money is just for [expr], or does it include [expr~] and/or
> [fexpr~] as well. The task description should be made clearer.
What I would
I wrote "[expr] family replacement", which may have been ambiguous-- I meant
"expr family replacement", as in [expr], [expr~], and [fexpr~]. And as I
wrote, 3 / 2 must equal 1.5.
-Jonathan
- Original Message -
> From: Mathieu Bouchard
> To: pd-list@iem.at
> Cc: Andy Farnell ; Jonath
On Sat, 12 Nov 2011 13:21:29 -0800
Marvin Humphrey wrote:
> On Sat, Nov 12, 2011 at 03:24:27PM -0500, Mathieu Bouchard wrote:
> > btw, I haven't seen any of the three funders (Andy, Jonathan, Marvin) say
> > whether their money is just for [expr], or does it include [expr~] and/or
> > [fexpr~]
Le 2011-11-12 à 13:32:00, Jonathan Wilkes a écrit :
I wrote "[expr] family replacement", which may have been ambiguous
Oh, no, it was clear, but I forgot about it, because 2 out of 3 people
didn't specify.
__
| Mathieu BOU
This may have come up before, but I didn't see a clear answer to this on
searches.
I've been doing more work involving the dynamic creation of abstractions
numbering greater than 1000; these involve using [soundfiler], so I've been
putting [del 1] between each creation message. This may be extrane
21 matches
Mail list logo
