Patches item #1575544, was opened at 2006-10-11 17:29
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1575544&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: bugfix
Status: Open
Resolution: None
Priority: 5
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: Fix to build Pd-0.40 on Mac OS X 10.4/PowerPC
Initial Comment:
According to this doc:
http://developer.apple.com/documentation/Porting/Conceptual/PortingUnix/com…
This needs to be added to the CFLAGS "-isysroot
/Developer/SDKs/MacOSX10.4u.sdk". I can't build
pd-0.40 on a 10.4 PowerPC machine because it complains
about this. I think the addition of this flag won't
break Intel compilation because I think its the default
setting on 10.4/Intel already.
Basically this line in configure.in needs to change from:
MORECFLAGS="-arch i386 -arch ppc -Wno-error"
to this:
MORECFLAGS="-isysroot
/Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc
-Wno-error"
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1575544&group_…
Bugs item #1483759, was opened at 2006-05-08 14:01
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1483759&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pd-extended
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: /bin/pthreadVC.dll missing
Initial Comment:
/bin/pthreadVC.dll is missing. Copying it from any
other pd version solves the problem.
jmmmp
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-10-11 09:25
Message:
Logged In: YES
user_id=564396
is this still open?
----------------------------------------------------------------------
Comment By: SourceForge Robot (sf-robot)
Date: 2006-06-01 04:21
Message:
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2006-05-17 13:33
Message:
Logged In: NO
well, since it's a dll, windows for sure. I guess the same
version as in ZÃŒrich, 0.39t3. Which I can check only on the
command line, because when I go to help-about the version
isn't there, just the string "PD_VERSION"
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2006-05-17 11:39
Message:
Logged In: YES
user_id=27104
Where is it missing from? What release? What OS? What version?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1483759&group_…
Bugs item #1561839, was opened at 2006-09-20 03:31
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1561839&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: v0.40.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Nobody/Anonymous (nobody)
Summary: rhythmic glitching on PowerBook G4
Initial Comment:
On an Apple PowerBook G4 1.67GHz running 10.4.7, the
sound always had a pulsing glitch on it no matter if
any sound was being generated or not. When I switched
the output sampling rate to 48000, the glitching went
away. When I switched back to 44100, the glitching
came back.
I saw this one other time on a PowerBook, but it was
also happening to Audacity. This time it was only
happening for Pd. My guess is that its related to
portaudio.
This was on a student's laptop, so I can't test again.
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-10-11 09:22
Message:
Logged In: YES
user_id=564396
experienced something similar on a G4 iBook (of a student,
so don't ask for details...) with an RME fireface.
this only happened with pd-extended (if i only knew the
version...0.38, 0.39??), running vanilla pd-0.39-2 did solve
the problem.
the test was the "test audio and midi" sinewaves.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1561839&group_…
Bugs item #1494449, was opened at 2006-05-24 19:03
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1494449&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Pending
Resolution: None
Priority: 5
Submitted By: christopher clepper (cclepper)
Assigned to: Nobody/Anonymous (nobody)
Summary: configure script change for intel Mac
Initial Comment:
Attached diff to detect for x86 or PowerPc based Macs
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-10-10 17:16
Message:
Logged In: YES
user_id=564396
set to pending;
is this a bug-report or really just a "patch" ....?
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-08-31 10:10
Message:
Logged In: YES
user_id=564396
it seems like this is now handled differently.
should this bug-report be therefore closed?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1494449&group_…
Bugs item #1518030, was opened at 2006-07-06 11:54
Message generated for change (Settings changed) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1518030&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: v0.40.1
Status: Open
Resolution: None
Priority: 7
Submitted By: ClaudiusMaximus (claudiusmaximus)
>Assigned to: Miller Puckette (millerpuckette)
Summary: subpatch clearing itself crashes Pd
Initial Comment:
Tested on Linux with pd-0.39-2 from Miller's site.
Steps to reproduce:
start pd
load the patch attached to this post
click the bng
close the patch
load the patch again
click the bng
=> crash
OR
start pd
load the patch
open the subpatch
(optionally: close the subpatch)
click the bng
=> crash
Here's a gdb backtrace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 27794)]
pd_bang (x=0x11) at m_pd.c:269
269 m_pd.c: No such file or directory.
in m_pd.c
(gdb) where
#0 pd_bang (x=0x11) at m_pd.c:269
#1 0x0808a61b in outlet_bang (x=0x3) at m_obj.c:328
#2 0x080765ad in bng_bout2 (x=0x81f2790) at g_bang.c:294
#3 0x080767f6 in bng_newclick (z=0x11,
glist=0x81f2338, xpix=74, ypix=70,
shift=0, alt=0, dbl=0, doit=1) at g_bang.c:343
#4 0x0806e907 in gobj_click (x=0x0, glist=0x11,
xpix=17, ypix=17, shift=17,
alt=17, dbl=17, doit=17) at g_editor.c:92
#5 0x0805b557 in graph_click (z=0x81f2338, glist=0x11,
xpix=74, ypix=70,
shift=0, alt=0, dbl=17, doit=1) at g_graph.c:1059
#6 0x0806e907 in gobj_click (x=0x0, glist=0x11,
xpix=17, ypix=17, shift=17,
alt=17, dbl=17, doit=17) at g_editor.c:92
#7 0x08070a97 in canvas_doclick (x=0x81ecd08, xpos=74,
ypos=70, which=1,
mod=0, doit=1) at g_editor.c:1094
#8 0x0807119d in canvas_mousedown (x=0x11, xpos=0,
ypos=0, which=0, mod=0)
at g_editor.c:1252
#9 0x08089789 in pd_typedmess (x=0x81ecd08, s=0x0,
argc=0, argv=0x80cf488)
at m_class.c:728
#10 0x08089665 in pd_typedmess (x=0x81f25f8, s=0x0,
argc=4, argv=0x80cf468)
at m_class.c:749
#11 0x0808c32f in binbuf_eval (x=0x11,
target=0x81f25f8, argc=0, argv=0x0)
at m_binbuf.c:574
#12 0x08091fdf in socketreceiver_read (x=0x81ec2f0,
fd=7) at s_inter.c:540
#13 0x0809180f in sys_domicrosleep (microsec=17,
pollem=1) at s_inter.c:180
#14 0x08092660 in sys_pollgui () at s_inter.c:823
#15 0x0808fe5b in m_scheduler () at m_sched.c:466
#16 0x08095b1b in main (argc=17, argv=0x11) at s_entry.c:27
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-10-10 17:13
Message:
Logged In: YES
user_id=564396
the really interesting thing here, is that your patch will
not crash when you only click on the [bng] once. you have to
follow the steps as described.
i add another patch that triggers the crash reliable and
without the complicated procedure (just click it and crash it)
raised priority, since crashers should be fixed.
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-07-06 20:48
Message:
Logged In: YES
user_id=564396
this has nothing to do with GOP, therefore i renamed the
bug-report.
what happens: an object emits a message; the calling
function is pushed to the stack; the message triggers the
deletion of the object; after the message is done, the
calling function (of the now deleted object) is popped back
from the stack: but alas! the entire environment has changed
and nothing is as it should be....stack corruption -> crash.
personally i think, that this is NOT a bug in pd but rather
a bug in the patch (but i am repeating myself...)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1518030&group_…
Bugs item #1518030, was opened at 2006-07-06 11:54
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1518030&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
>Group: v0.40.1
Status: Open
Resolution: None
>Priority: 7
Submitted By: ClaudiusMaximus (claudiusmaximus)
Assigned to: Nobody/Anonymous (nobody)
Summary: subpatch clearing itself crashes Pd
Initial Comment:
Tested on Linux with pd-0.39-2 from Miller's site.
Steps to reproduce:
start pd
load the patch attached to this post
click the bng
close the patch
load the patch again
click the bng
=> crash
OR
start pd
load the patch
open the subpatch
(optionally: close the subpatch)
click the bng
=> crash
Here's a gdb backtrace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 27794)]
pd_bang (x=0x11) at m_pd.c:269
269 m_pd.c: No such file or directory.
in m_pd.c
(gdb) where
#0 pd_bang (x=0x11) at m_pd.c:269
#1 0x0808a61b in outlet_bang (x=0x3) at m_obj.c:328
#2 0x080765ad in bng_bout2 (x=0x81f2790) at g_bang.c:294
#3 0x080767f6 in bng_newclick (z=0x11,
glist=0x81f2338, xpix=74, ypix=70,
shift=0, alt=0, dbl=0, doit=1) at g_bang.c:343
#4 0x0806e907 in gobj_click (x=0x0, glist=0x11,
xpix=17, ypix=17, shift=17,
alt=17, dbl=17, doit=17) at g_editor.c:92
#5 0x0805b557 in graph_click (z=0x81f2338, glist=0x11,
xpix=74, ypix=70,
shift=0, alt=0, dbl=17, doit=1) at g_graph.c:1059
#6 0x0806e907 in gobj_click (x=0x0, glist=0x11,
xpix=17, ypix=17, shift=17,
alt=17, dbl=17, doit=17) at g_editor.c:92
#7 0x08070a97 in canvas_doclick (x=0x81ecd08, xpos=74,
ypos=70, which=1,
mod=0, doit=1) at g_editor.c:1094
#8 0x0807119d in canvas_mousedown (x=0x11, xpos=0,
ypos=0, which=0, mod=0)
at g_editor.c:1252
#9 0x08089789 in pd_typedmess (x=0x81ecd08, s=0x0,
argc=0, argv=0x80cf488)
at m_class.c:728
#10 0x08089665 in pd_typedmess (x=0x81f25f8, s=0x0,
argc=4, argv=0x80cf468)
at m_class.c:749
#11 0x0808c32f in binbuf_eval (x=0x11,
target=0x81f25f8, argc=0, argv=0x0)
at m_binbuf.c:574
#12 0x08091fdf in socketreceiver_read (x=0x81ec2f0,
fd=7) at s_inter.c:540
#13 0x0809180f in sys_domicrosleep (microsec=17,
pollem=1) at s_inter.c:180
#14 0x08092660 in sys_pollgui () at s_inter.c:823
#15 0x0808fe5b in m_scheduler () at m_sched.c:466
#16 0x08095b1b in main (argc=17, argv=0x11) at s_entry.c:27
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-10-10 17:13
Message:
Logged In: YES
user_id=564396
the really interesting thing here, is that your patch will
not crash when you only click on the [bng] once. you have to
follow the steps as described.
i add another patch that triggers the crash reliable and
without the complicated procedure (just click it and crash it)
raised priority, since crashers should be fixed.
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-07-06 20:48
Message:
Logged In: YES
user_id=564396
this has nothing to do with GOP, therefore i renamed the
bug-report.
what happens: an object emits a message; the calling
function is pushed to the stack; the message triggers the
deletion of the object; after the message is done, the
calling function (of the now deleted object) is popped back
from the stack: but alas! the entire environment has changed
and nothing is as it should be....stack corruption -> crash.
personally i think, that this is NOT a bug in pd but rather
a bug in the patch (but i am repeating myself...)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1518030&group_…
Patches item #1549377, was opened at 2006-08-30 17:39
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1549377&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: bugfix
Status: Open
Resolution: None
>Priority: 7
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: fix crash on sending empty "obj" mesage to closed canvas
Initial Comment:
as described in bug #1525832, pd crashes when you send
a "msg" or "obj" message (without coordinates and
arguments) to a canvas that is not visible (e.g. closed).
this is due to the fact, that inthis case, pd
automatically goes into edit mode, so you can type in
the content of the object/message (it's like creating
an empty object-box with Ctrl-1).
this is a not so clever thing, when the canvas is closed.
attached is a patch that fixes this, by checking
whether the canvas is visible and refusing to continue
otherwise
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-10-10 15:28
Message:
Logged In: YES
user_id=564396
raised priority, since a crasher should be fixed.
added a patch to reliably reproduce the bug.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1549377&group_…
Bugs item #1427520, was opened at 2006-02-08 14:34
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1427520&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: abstractions
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Piotr Majdak (piotrmajdak)
>Assigned to: Miller Puckette (millerpuckette)
Summary: Link broken in Help patch for netsend
Initial Comment:
In netsend-help.pd is a link given, which seems to be
broken: ftp://fals.ch/pub/pdnets
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-10-10 15:21
Message:
Logged In: YES
user_id=564396
for intercommunication with max, i suggest to use OSC.
nevertheless, the link is really broken (fals.ch does not
exist anymore), and should therefore be removed from the
help-patch.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1427520&group_…
Bugs item #1508138, was opened at 2006-06-18 15:47
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1508138&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pd-extended
Group: v0.39.2
Status: Open
Resolution: None
Priority: 5
Submitted By: João Miguel Pais (jmmmp)
Assigned to: Nobody/Anonymous (nobody)
Summary: program crash leads to system crash
Initial Comment:
If pd crashes once (for whichever reason it may be),
when the program is loaded again a system error occurs,
and a blue screen appears.
The error message of the blue screen is
IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0X0000000A (0X00000004, 0X00000002,
0X00000000, 0X804E39A7)
Therefore, if pd crashes, it is necessary to reboot the
system in order to avoid a system crash (logging out
doesn't help).
Pd-ext 0.39-2 t3
XP Prof
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-10-10 15:13
Message:
Logged In: YES
user_id=564396
"I don't have a patch, because it was corrected already (I
don't remember now)."
does this mean that it works now?
can we close this?
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2006-06-19 08:49
Message:
Logged In: NO
then also try to test your RAM sanity, with software like
memtest86.... it could be a bad bank of ram...
----------------------------------------------------------------------
Comment By: João Miguel Pais (jmmmp)
Date: 2006-06-18 22:01
Message:
Logged In: YES
user_id=1523458
The problem has nothing to do with audio, as actually in
most of the cases I didn't had audio on. I don't have a
patch, because it was corrected already (I don't remember
now).
But the error that made pd crash the first time might had to
do with a cpu overload (or whatever is it called) due to an
infinite loop.
Which kind of hardware info is necessary? I guess saying IBM
Thinkpad R51 1,6Mhz 1GbRam doesn't help much.
----------------------------------------------------------------------
Comment By: Thomas Grill (xovo)
Date: 2006-06-18 19:24
Message:
Logged In: YES
user_id=350252
Although the information given about the crash is close to nothing (for
whichever reason that may be), it's almost certainly a driver bug, not a pure
pd bug. You should include info about what you are doing (include patches,
description etc.) and about your hardware. And you should try to find newer/
different drivers for your audio hardware and see if the problem persists.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1508138&group_…
Bugs item #1563095, was opened at 2006-09-21 21:13
Message generated for change (Settings changed) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1563095&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pd-extended
Group: v0.39.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Hans-Christoph Steiner (eighthave)
Summary: bug in iemlib's for++
Initial Comment:
There is a bug with the iemlib for++ object in PD-
extended:
I discovered a workaround to load for++ for now:
1. try to make an object [for++] -> PD will say that
there is no object like for++
2. try to make an object [forpp] -> PD will say that
there is no object like forpp
3. try again to make an object [for++] -> et viola ,
there is thefor++ I was looking for
cheers,
Nils
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2006-09-26 08:40
Message:
Logged In: NO
Not a fix, but another workaround: I've checked in a
for++.pd abstraction, which is compatible with the
IEMLIB-external. It's in the CVS at
http://pure-data.cvs.sourceforge.net/pure-data/abstractions/purepd/
ciao
-- fbar
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2006-09-22 16:01
Message:
Logged In: YES
user_id=27104
This is most likely because the class name is "for++", but
the source filename is "forpp.c". I think + is a valid
character for the filesystem, otherwise it could be renamed
using the hex loader.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1563095&group_…