Pd-dev May 2008

pd-dev@lists.iem.at

20 participants
187 discussions

[ pure-data-Bugs-1976100 ] colorgrid not working on osx
by SourceForge.net 28 May '08

28 May '08

Bugs item #1976100, was opened at 2008-05-28 08:39 Message generated for change (Comment added) made by stffn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1976100&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 Private: No Submitted By: stffn (stffn) Assigned to: Hans-Christoph Steiner (eighthave) Summary: colorgrid not working on osx Initial Comment: colorgrid is not working properly on intel mac osx running Pd-extended 0.40.3 22th of May build. It does output the RGB values when moving the red square around the grid but the there is no colors in the grid so it's fairly pointless. (still no 0.40.3 group to choose from in the dropdown) ---------------------------------------------------------------------- >Comment By: stffn (stffn) Date: 2008-05-28 08:40 Message: Logged In: YES user_id=1658640 Originator: YES That is pdp_colorgrid of cause. Sorry. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1976100&group_…

1 0

[ pure-data-Bugs-1976100 ] colorgrid not working on osx
by SourceForge.net 28 May '08

28 May '08

Bugs item #1976100, was opened at 2008-05-28 08:39 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1976100&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 Private: No Submitted By: stffn (stffn) Assigned to: Hans-Christoph Steiner (eighthave) Summary: colorgrid not working on osx Initial Comment: colorgrid is not working properly on intel mac osx running Pd-extended 0.40.3 22th of May build. It does output the RGB values when moving the red square around the grid but the there is no colors in the grid so it's fairly pointless. (still no 0.40.3 group to choose from in the dropdown) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1976100&group_…

1 0

[ pure-data-Patches-1975056 ] show whole subpatch name in window title
by SourceForge.net 27 May '08

27 May '08

Patches item #1975056, was opened at 2008-05-27 11:18 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=1975056&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: None Status: Open Resolution: None Priority: 4 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: Miller Puckette (millerpuckette) Summary: show whole subpatch name in window title Initial Comment: Since you can type a whole long list of atoms in the subpatch object box, it is also useful to show this whole name in the window title. This patch does that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1975056&group_…

1 0

bang [block~] to query current blocksize
by Hans-Christoph Steiner 27 May '08

27 May '08

I just had a thought, what about adding an outlet to [block~] that will output the block size as a float when [block~] is banged? I can't think of any other way to query what the current block size is, and it would be useful sometimes. .hc ------------------------------------------------------------------------ ---- "[T]he greatest purveyor of violence in the world today [is] my own government." - Martin Luther King, Jr.

7 21

LuaJIT
by Frank Barknecht 26 May '08

26 May '08

Hi lsit/Claude, attached is a toy variation of pdlua's "Makefile.static" which builds pdlua statically linked to LuaJIT, the optimizing JIT compiler for Lua. Only tested on Linux. LuaJIT can be quite a performance boost. It's probably good to install the jit/opt*.lua modules as well according to http://luajit.org/luajit_install.html Ciao -- Frank Barknecht _ ______footils.org__

1 0

[ pure-data-Patches-1930733 ] 0.41-4: prevent buffer overrun in m_class.c
by SourceForge.net 26 May '08

26 May '08

Patches item #1930733, was opened at 2008-03-31 18:02 Message generated for change (Comment added) made by millerpuckette You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1930733&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 Private: No Submitted By: Thomas Grill (xovo) Assigned to: Miller Puckette (millerpuckette) Summary: 0.41-4: prevent buffer overrun in m_class.c Initial Comment: the array only has MAXPDARG elements....... --- m_class.ori.c 2008-04-01 03:00:09.000000000 +0200 +++ m_class.c 2008-04-01 03:00:12.000000000 +0200 @@ -763,7 +763,7 @@ va_start(ap, fmt); while (1) { - if (nargs > MAXPDARG) + if (nargs >= MAXPDARG) { pd_error(x, "pd_vmess: only %d allowed", MAXPDARG); break; ---------------------------------------------------------------------- >Comment By: Miller Puckette (millerpuckette) Date: 2008-05-26 09:46 Message: Logged In: YES user_id=313747 Originator: NO It will work fine to allow MAXARG+1 arguments (6) to vmess; the MAXARGS restriction in typedmess() is unrelated. I think that's the best way since apparently some code exists that depends on MAXARG+1. It's not clear what the maximum should really be; since this is a convenience routine anyway, I'm thinking it should be expanded, say to 10 or so. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-05-26 08:57 Message: Logged In: YES user_id=27104 Originator: NO It seems to me that the logic of the function needs to change, but adding +1 to the array will prevent the overflow, though it's not a very clean way to do it. Works for now, I suppose. ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2008-05-26 00:32 Message: Logged In: YES user_id=564396 Originator: NO as thomas has pointed out, there _is_ a buffer overrun which should be fixed rather than merely unapplying the patch because it gives weird error messages. so for the ease of applying it, here is the patch that fixes the leak by adding an additional element to the array (i'll apply it to pd-ext 0.40) Index: m_class.c =================================================================== --- m_class.c (Revision 9919) +++ m_class.c (Arbeitskopie) @@ -772,7 +772,7 @@ void pd_vmess(t_pd *x, t_symbol *sel, char *fmt, ...) { va_list ap; - t_atom arg[MAXPDARG], *at =arg; + t_atom arg[MAXPDARG+1], *at =arg; int nargs = 0; char *fp = fmt; ---------------------------------------------------------------------- Comment By: Thomas Grill (xovo) Date: 2008-05-26 00:17 Message: Logged In: YES user_id=350252 Originator: YES Is the arg array too small then and must have MAXPDARGS+1 elements instead? In the loop, the "at" pointer subsequently points to the elements of "arg". If the switch statement is reached with a value of "nargs == MAXPDARG", then "arg" points to a position outside the array. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-05-25 14:52 Message: Logged In: YES user_id=27104 Originator: NO This patch causes this message when clicking on abstractions and subpatches in run mode: error: pd_vmess: only 5 allowed ... you might be able to track this down from the Find menu. I think this patch might be invalid since nargs is only used to send to typedmess() as argc, in which case 5 is the appropriate value. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-04-15 16:42 Message: Logged In: YES user_id=27104 Originator: NO checked into branches/pd-extended/0.40 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1930733&group_…

1 0

[ pure-data-Patches-1930733 ] 0.41-4: prevent buffer overrun in m_class.c
by SourceForge.net 26 May '08

26 May '08

Patches item #1930733, was opened at 2008-03-31 21:02 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1930733&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 Private: No Submitted By: Thomas Grill (xovo) Assigned to: Miller Puckette (millerpuckette) Summary: 0.41-4: prevent buffer overrun in m_class.c Initial Comment: the array only has MAXPDARG elements....... --- m_class.ori.c 2008-04-01 03:00:09.000000000 +0200 +++ m_class.c 2008-04-01 03:00:12.000000000 +0200 @@ -763,7 +763,7 @@ va_start(ap, fmt); while (1) { - if (nargs > MAXPDARG) + if (nargs >= MAXPDARG) { pd_error(x, "pd_vmess: only %d allowed", MAXPDARG); break; ---------------------------------------------------------------------- >Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-05-26 11:57 Message: Logged In: YES user_id=27104 Originator: NO It seems to me that the logic of the function needs to change, but adding +1 to the array will prevent the overflow, though it's not a very clean way to do it. Works for now, I suppose. ---------------------------------------------------------------------- Comment By: IOhannes m zmölnig (zmoelnig) Date: 2008-05-26 03:32 Message: Logged In: YES user_id=564396 Originator: NO as thomas has pointed out, there _is_ a buffer overrun which should be fixed rather than merely unapplying the patch because it gives weird error messages. so for the ease of applying it, here is the patch that fixes the leak by adding an additional element to the array (i'll apply it to pd-ext 0.40) Index: m_class.c =================================================================== --- m_class.c (Revision 9919) +++ m_class.c (Arbeitskopie) @@ -772,7 +772,7 @@ void pd_vmess(t_pd *x, t_symbol *sel, char *fmt, ...) { va_list ap; - t_atom arg[MAXPDARG], *at =arg; + t_atom arg[MAXPDARG+1], *at =arg; int nargs = 0; char *fp = fmt; ---------------------------------------------------------------------- Comment By: Thomas Grill (xovo) Date: 2008-05-26 03:17 Message: Logged In: YES user_id=350252 Originator: YES Is the arg array too small then and must have MAXPDARGS+1 elements instead? In the loop, the "at" pointer subsequently points to the elements of "arg". If the switch statement is reached with a value of "nargs == MAXPDARG", then "arg" points to a position outside the array. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-05-25 17:52 Message: Logged In: YES user_id=27104 Originator: NO This patch causes this message when clicking on abstractions and subpatches in run mode: error: pd_vmess: only 5 allowed ... you might be able to track this down from the Find menu. I think this patch might be invalid since nargs is only used to send to typedmess() as argc, in which case 5 is the appropriate value. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-04-15 19:42 Message: Logged In: YES user_id=27104 Originator: NO checked into branches/pd-extended/0.40 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1930733&group_…

1 0

[ pure-data-Patches-1930733 ] 0.41-4: prevent buffer overrun in m_class.c
by SourceForge.net 26 May '08

26 May '08

Patches item #1930733, was opened at 2008-04-01 03:02 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1930733&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 Private: No Submitted By: Thomas Grill (xovo) Assigned to: Miller Puckette (millerpuckette) Summary: 0.41-4: prevent buffer overrun in m_class.c Initial Comment: the array only has MAXPDARG elements....... --- m_class.ori.c 2008-04-01 03:00:09.000000000 +0200 +++ m_class.c 2008-04-01 03:00:12.000000000 +0200 @@ -763,7 +763,7 @@ va_start(ap, fmt); while (1) { - if (nargs > MAXPDARG) + if (nargs >= MAXPDARG) { pd_error(x, "pd_vmess: only %d allowed", MAXPDARG); break; ---------------------------------------------------------------------- >Comment By: IOhannes m zmölnig (zmoelnig) Date: 2008-05-26 09:32 Message: Logged In: YES user_id=564396 Originator: NO as thomas has pointed out, there _is_ a buffer overrun which should be fixed rather than merely unapplying the patch because it gives weird error messages. so for the ease of applying it, here is the patch that fixes the leak by adding an additional element to the array (i'll apply it to pd-ext 0.40) Index: m_class.c =================================================================== --- m_class.c (Revision 9919) +++ m_class.c (Arbeitskopie) @@ -772,7 +772,7 @@ void pd_vmess(t_pd *x, t_symbol *sel, char *fmt, ...) { va_list ap; - t_atom arg[MAXPDARG], *at =arg; + t_atom arg[MAXPDARG+1], *at =arg; int nargs = 0; char *fp = fmt; ---------------------------------------------------------------------- Comment By: Thomas Grill (xovo) Date: 2008-05-26 09:17 Message: Logged In: YES user_id=350252 Originator: YES Is the arg array too small then and must have MAXPDARGS+1 elements instead? In the loop, the "at" pointer subsequently points to the elements of "arg". If the switch statement is reached with a value of "nargs == MAXPDARG", then "arg" points to a position outside the array. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-05-25 23:52 Message: Logged In: YES user_id=27104 Originator: NO This patch causes this message when clicking on abstractions and subpatches in run mode: error: pd_vmess: only 5 allowed ... you might be able to track this down from the Find menu. I think this patch might be invalid since nargs is only used to send to typedmess() as argc, in which case 5 is the appropriate value. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-04-16 01:42 Message: Logged In: YES user_id=27104 Originator: NO checked into branches/pd-extended/0.40 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1930733&group_…

1 0

[ pure-data-Patches-1930733 ] 0.41-4: prevent buffer overrun in m_class.c
by SourceForge.net 26 May '08

26 May '08

Patches item #1930733, was opened at 2008-04-01 01:02 Message generated for change (Settings changed) made by xovo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1930733&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 Private: No Submitted By: Thomas Grill (xovo) >Assigned to: Miller Puckette (millerpuckette) Summary: 0.41-4: prevent buffer overrun in m_class.c Initial Comment: the array only has MAXPDARG elements....... --- m_class.ori.c 2008-04-01 03:00:09.000000000 +0200 +++ m_class.c 2008-04-01 03:00:12.000000000 +0200 @@ -763,7 +763,7 @@ va_start(ap, fmt); while (1) { - if (nargs > MAXPDARG) + if (nargs >= MAXPDARG) { pd_error(x, "pd_vmess: only %d allowed", MAXPDARG); break; ---------------------------------------------------------------------- Comment By: Thomas Grill (xovo) Date: 2008-05-26 07:17 Message: Logged In: YES user_id=350252 Originator: YES Is the arg array too small then and must have MAXPDARGS+1 elements instead? In the loop, the "at" pointer subsequently points to the elements of "arg". If the switch statement is reached with a value of "nargs == MAXPDARG", then "arg" points to a position outside the array. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-05-25 21:52 Message: Logged In: YES user_id=27104 Originator: NO This patch causes this message when clicking on abstractions and subpatches in run mode: error: pd_vmess: only 5 allowed ... you might be able to track this down from the Find menu. I think this patch might be invalid since nargs is only used to send to typedmess() as argc, in which case 5 is the appropriate value. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-04-15 23:42 Message: Logged In: YES user_id=27104 Originator: NO checked into branches/pd-extended/0.40 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1930733&group_…

1 0

[ pure-data-Patches-1930733 ] 0.41-4: prevent buffer overrun in m_class.c
by SourceForge.net 26 May '08

26 May '08

Patches item #1930733, was opened at 2008-04-01 01:02 Message generated for change (Settings changed) made by xovo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1930733&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: Invalid Priority: 7 Private: No Submitted By: Thomas Grill (xovo) Assigned to: Thomas Grill (xovo) Summary: 0.41-4: prevent buffer overrun in m_class.c Initial Comment: the array only has MAXPDARG elements....... --- m_class.ori.c 2008-04-01 03:00:09.000000000 +0200 +++ m_class.c 2008-04-01 03:00:12.000000000 +0200 @@ -763,7 +763,7 @@ va_start(ap, fmt); while (1) { - if (nargs > MAXPDARG) + if (nargs >= MAXPDARG) { pd_error(x, "pd_vmess: only %d allowed", MAXPDARG); break; ---------------------------------------------------------------------- >Comment By: Thomas Grill (xovo) Date: 2008-05-26 07:17 Message: Logged In: YES user_id=350252 Originator: YES Is the arg array too small then and must have MAXPDARGS+1 elements instead? In the loop, the "at" pointer subsequently points to the elements of "arg". If the switch statement is reached with a value of "nargs == MAXPDARG", then "arg" points to a position outside the array. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-05-25 21:52 Message: Logged In: YES user_id=27104 Originator: NO This patch causes this message when clicking on abstractions and subpatches in run mode: error: pd_vmess: only 5 allowed ... you might be able to track this down from the Find menu. I think this patch might be invalid since nargs is only used to send to typedmess() as argc, in which case 5 is the appropriate value. ---------------------------------------------------------------------- Comment By: Hans-Christoph Steiner (eighthave) Date: 2008-04-15 23:42 Message: Logged In: YES user_id=27104 Originator: NO checked into branches/pd-extended/0.40 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1930733&group_…

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pd-dev May 2008