Bugs item #2021648, was opened at 2008-07-18 17:05
Message generated for change (Comment added) made by sf-robot
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2021648&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: externals
Group: None
>Status: Closed
Resolution: Accepted
Priority: 5
Private: No
Submitted By: Federico Ferri (federico__)
Assigned to: IOhannes m zmlnig (zmoelnig)
Summary: zexy: configure.ac: $LDFLAGS in wrong place
Initial Comment:
line 425 of configure.ac:
LFLAGS=${LDFLAGS}
is wrong.
LDFLAGS are passed to gcc, not to ld.
I have in my LDFLAGS -Wl,-O1, which make ld fail.
ld should only see the -O1 option
make output:
i686-pc-linux-gnu-ld -shared --export-dynamic -Wl,-O1 -o zexy.pd_linux *.o -lm -lc
i686-pc-linux-gnu-ld: unrecognized option '-Wl,-O1'
i686-pc-linux-gnu-ld: use the --help option for usage information
make: *** [zexy] Error 1
please fix. (you can fix it by making an empty LFLAGS)
----------------------------------------------------------------------
>Comment By: SourceForge Robot (sf-robot)
Date: 2008-08-07 02:20
Message:
Logged In: YES
user_id=1312539
Originator: NO
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: IOhannes m zmlnig (zmoelnig)
Date: 2008-07-23 07:10
Message:
Logged In: YES
user_id=564396
Originator: NO
good that you have found a solution.
2 remarks:
- i kind of started to migrate the build-system from zexy/src/ to
zexy/build/autoconf/ and incorporated your changes there.
i suggest you just use this build-system from now on.
- i am not so sure whether using $(CC) as linker is truely portable; not
every compiler might be able to implicitely run a linker, like gcc.
if you feel unhappy with this solution (using build/autoconf/), just
re-open this ticket.
----------------------------------------------------------------------
Comment By: Federico Ferri (federico__)
Date: 2008-07-22 19:47
Message:
Logged In: YES
user_id=1628983
Originator: YES
so, finally, I managed to fix your problem.
replace $(LD) with $(CC) in Makefile and you are okay, there's no need of
transforming variables or such. here's the one-liner fix I use in the
Gentoo Ebuild:
sed -i -e 's/\$(LD)/\$(CC)/g' Makefile
you can always check here [1] how do I build externals. please notify me
when you commit this little fix, so I remove the fix from the ebuild.
[1]
http://pd-overlay.svn.sourceforge.net/viewvc/pd-overlay/pd-overlay/media-pl…
(actually Sf's ViewVC is down)
----------------------------------------------------------------------
Comment By: Federico Ferri (federico__)
Date: 2008-07-21 17:08
Message:
Logged In: YES
user_id=1628983
Originator: YES
hi IOhannes,
I'm not sure what you should do; the 'GNU Coding Standards' document
doesn't make mention of this (I generally look-up there things when I'm in
doubt).
As I explained, the $(LDFLAGS) has to be passed to gcc, not to ld.
For example, if you have -Wl,--as-needed in $LDFLAGS, the ld program only
wants to see --as-needed.
There are two options:
1) [PROBABLY BAD] if you want to pass $LDFLAGS directly to linker, you
have to turn the "-Wl,--flag1,--flag2" option into "--flag1 --flag2".
I don't see a handy way to do it.
2) use gcc to do the linking.
please read this excerpt from `man ld`:
------------------------------------------------------------------------------
Note---if the linker is being invoked indirectly, via a compiler
driver
(e.g. gcc) then all the linker command line options should be
prefixed
by -Wl, (or whatever is appropriate for the particular compiler
driver)
like this:
gcc -Wl,--startgroup foo.o bar.o -Wl,--endgroup
This is important, because otherwise the compiler driver program
may
silently drop the linker options, resulting in a bad link.
------------------------------------------------------------------------------
also, beware that using a LFLAGS in Makefile could give you weird results,
since LFLAGS are the Lex-flags (that's not your case, since configure is
just a shell script, but just to inform you ;)
so, in my opinion, you should use $(CC) to link objects.
now I'm asking to some people on IRC but still didn't get a reply. if I'll
eventually get a better answer I'll add a comment here.
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-07-21 13:29
Message:
Logged In: YES
user_id=564396
Originator: NO
do you have any reference tpo the correct use of LFLAGS vs LDFLAGS?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2021648&group_…
Bugs item #1577739, was opened at 2006-10-15 20:42
Message generated for change (Comment added) made by fbar
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&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: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Frank Barknecht (fbar)
>Assigned to: Nobody/Anonymous (nobody)
Summary: Malformed data at end of patch is treated as sender
Initial Comment:
When opening a patch file Pd doesn't check correctly if
all messages are well-formed. Inserting a line at end
of a patch file, that starts with a symbol and ends
with a ";" will treat the leading symbol as a
receive-target and will send the rest of the line to
that receiver.
For example inserting:
pd dsp 1;
at the end of a patch will switch on audio, even when
the patch is started with "pd -noloadbang".
While this message is harmless, other messages may do
nasty things and open a security hole.
Attached is a patch that illustrates this behaviour,
also see this pd-list message thread:
http://lists.puredata.info/pipermail/pd-list/2006-10/043161.html
----------------------------------------------------------------------
>Comment By: Frank Barknecht (fbar)
Date: 2008-08-05 13:41
Message:
Logged In: YES
user_id=569446
Originator: YES
I see. Okay, I think, then we can savely mark this report as invalid and
close it.
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-05 09:57
Message:
Logged In: YES
user_id=564396
Originator: NO
i think there is a clarification needed:
the behaviour you are expecting is _not_ limited to the end of patch
(EOP).
it can just occur anywhere within the patch:
the reason is simple: in reality the "#X" is really just a receiver where
the objectmaker is bound to: it does receives messages from the patch, just
like in your example.
and of course there is a well known example in Pd itself that uses this
mechanism: array!
the "#A" is really just a receiver that is bound to the latest created
array (you can check by creating a new array "foo" and then send a message
[; #A 0 10 20 30 40 50()
when storing a patch, the array will just dump it's data in a form that it
is able to receive.
when reading the patch, the array is bound to the #A and receives the data
it has previously dumped.
ftm does it very similar.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2008-08-05 09:46
Message:
Logged In: YES
user_id=569446
Originator: YES
I didn't know about or think of this use case, which definitely is
interesting.
Some more questions: You write "if objects forget about these messages it
is rather broken objects ..." I thought, Pd itself forgets the data at the
end, not certain objects in Pd or am I wrong?
Then: Currently it seems, only FTM uses the space at the end of a patch
("EOP"?) to store additional data. I didn't yet check how FTM does this,
but what if other objects also start using the EOP-data? Could this lead to
conflicts where one object overwrites data of another object? I think, with
Pd's traditional way of storing data in #-lines, this generally cannot
happen.
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 19:44
Message:
Logged In: YES
user_id=564396
Originator: NO
even if matju thinks you can use [loadbang] for these kind of things, he
might be wrong here.
the sent messages are sent immediately (even before a hypothetic
[initbang] message!), whereas the loadbang is delayed rather long. (as we
all now)
as claude has pointed out, the "freer than max" talk should show (i hope)
that you can really do cool things with this additional data, which you
could not do with any other "elegant" method i know.
if objects forget about these messages it is rather broken objects than a
bug in Pd.
(e.g. the FTM-objects happily save (and recall) the data via this
send-"hack")
----------------------------------------------------------------------
Comment By: ClaudiusMaximus (claudiusmaximus)
Date: 2008-08-04 19:18
Message:
Logged In: YES
user_id=769033
Originator: NO
I think it is a feature too - if I recall correctly, the "Freer Than Max:
Porting FTM to Pure-data" presentation at LAC showed that externals can
save additional data to a Pd patch, using precisely this feature to
re-access it on load.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2008-08-04 19:01
Message:
Logged In: YES
user_id=569446
Originator: YES
But as a feature it is rather broken, because the data at the end of the
file is deleted if you save the patch from Pd. And even the feature can be
build in Pd itself with a loadbang'd semicolon-message box, as matju
pointed out here:
http://lists.puredata.info/pipermail/pd-list/2006-10/043171.html
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 18:45
Message:
Logged In: YES
user_id=564396
Originator: NO
i think this is a feature
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&group_…
Bugs item #1577739, was opened at 2006-10-15 20:42
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&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: 5
Private: No
Submitted By: Frank Barknecht (fbar)
Assigned to: Miller Puckette (millerpuckette)
Summary: Malformed data at end of patch is treated as sender
Initial Comment:
When opening a patch file Pd doesn't check correctly if
all messages are well-formed. Inserting a line at end
of a patch file, that starts with a symbol and ends
with a ";" will treat the leading symbol as a
receive-target and will send the rest of the line to
that receiver.
For example inserting:
pd dsp 1;
at the end of a patch will switch on audio, even when
the patch is started with "pd -noloadbang".
While this message is harmless, other messages may do
nasty things and open a security hole.
Attached is a patch that illustrates this behaviour,
also see this pd-list message thread:
http://lists.puredata.info/pipermail/pd-list/2006-10/043161.html
----------------------------------------------------------------------
>Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-05 09:57
Message:
Logged In: YES
user_id=564396
Originator: NO
i think there is a clarification needed:
the behaviour you are expecting is _not_ limited to the end of patch
(EOP).
it can just occur anywhere within the patch:
the reason is simple: in reality the "#X" is really just a receiver where
the objectmaker is bound to: it does receives messages from the patch, just
like in your example.
and of course there is a well known example in Pd itself that uses this
mechanism: array!
the "#A" is really just a receiver that is bound to the latest created
array (you can check by creating a new array "foo" and then send a message
[; #A 0 10 20 30 40 50()
when storing a patch, the array will just dump it's data in a form that it
is able to receive.
when reading the patch, the array is bound to the #A and receives the data
it has previously dumped.
ftm does it very similar.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2008-08-05 09:46
Message:
Logged In: YES
user_id=569446
Originator: YES
I didn't know about or think of this use case, which definitely is
interesting.
Some more questions: You write "if objects forget about these messages it
is rather broken objects ..." I thought, Pd itself forgets the data at the
end, not certain objects in Pd or am I wrong?
Then: Currently it seems, only FTM uses the space at the end of a patch
("EOP"?) to store additional data. I didn't yet check how FTM does this,
but what if other objects also start using the EOP-data? Could this lead to
conflicts where one object overwrites data of another object? I think, with
Pd's traditional way of storing data in #-lines, this generally cannot
happen.
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 19:44
Message:
Logged In: YES
user_id=564396
Originator: NO
even if matju thinks you can use [loadbang] for these kind of things, he
might be wrong here.
the sent messages are sent immediately (even before a hypothetic
[initbang] message!), whereas the loadbang is delayed rather long. (as we
all now)
as claude has pointed out, the "freer than max" talk should show (i hope)
that you can really do cool things with this additional data, which you
could not do with any other "elegant" method i know.
if objects forget about these messages it is rather broken objects than a
bug in Pd.
(e.g. the FTM-objects happily save (and recall) the data via this
send-"hack")
----------------------------------------------------------------------
Comment By: ClaudiusMaximus (claudiusmaximus)
Date: 2008-08-04 19:18
Message:
Logged In: YES
user_id=769033
Originator: NO
I think it is a feature too - if I recall correctly, the "Freer Than Max:
Porting FTM to Pure-data" presentation at LAC showed that externals can
save additional data to a Pd patch, using precisely this feature to
re-access it on load.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2008-08-04 19:01
Message:
Logged In: YES
user_id=569446
Originator: YES
But as a feature it is rather broken, because the data at the end of the
file is deleted if you save the patch from Pd. And even the feature can be
build in Pd itself with a loadbang'd semicolon-message box, as matju
pointed out here:
http://lists.puredata.info/pipermail/pd-list/2006-10/043171.html
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 18:45
Message:
Logged In: YES
user_id=564396
Originator: NO
i think this is a feature
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&group_…
Bugs item #1577739, was opened at 2006-10-15 20:42
Message generated for change (Comment added) made by fbar
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&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: 5
Private: No
Submitted By: Frank Barknecht (fbar)
Assigned to: Miller Puckette (millerpuckette)
Summary: Malformed data at end of patch is treated as sender
Initial Comment:
When opening a patch file Pd doesn't check correctly if
all messages are well-formed. Inserting a line at end
of a patch file, that starts with a symbol and ends
with a ";" will treat the leading symbol as a
receive-target and will send the rest of the line to
that receiver.
For example inserting:
pd dsp 1;
at the end of a patch will switch on audio, even when
the patch is started with "pd -noloadbang".
While this message is harmless, other messages may do
nasty things and open a security hole.
Attached is a patch that illustrates this behaviour,
also see this pd-list message thread:
http://lists.puredata.info/pipermail/pd-list/2006-10/043161.html
----------------------------------------------------------------------
>Comment By: Frank Barknecht (fbar)
Date: 2008-08-05 09:46
Message:
Logged In: YES
user_id=569446
Originator: YES
I didn't know about or think of this use case, which definitely is
interesting.
Some more questions: You write "if objects forget about these messages it
is rather broken objects ..." I thought, Pd itself forgets the data at the
end, not certain objects in Pd or am I wrong?
Then: Currently it seems, only FTM uses the space at the end of a patch
("EOP"?) to store additional data. I didn't yet check how FTM does this,
but what if other objects also start using the EOP-data? Could this lead to
conflicts where one object overwrites data of another object? I think, with
Pd's traditional way of storing data in #-lines, this generally cannot
happen.
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 19:44
Message:
Logged In: YES
user_id=564396
Originator: NO
even if matju thinks you can use [loadbang] for these kind of things, he
might be wrong here.
the sent messages are sent immediately (even before a hypothetic
[initbang] message!), whereas the loadbang is delayed rather long. (as we
all now)
as claude has pointed out, the "freer than max" talk should show (i hope)
that you can really do cool things with this additional data, which you
could not do with any other "elegant" method i know.
if objects forget about these messages it is rather broken objects than a
bug in Pd.
(e.g. the FTM-objects happily save (and recall) the data via this
send-"hack")
----------------------------------------------------------------------
Comment By: ClaudiusMaximus (claudiusmaximus)
Date: 2008-08-04 19:18
Message:
Logged In: YES
user_id=769033
Originator: NO
I think it is a feature too - if I recall correctly, the "Freer Than Max:
Porting FTM to Pure-data" presentation at LAC showed that externals can
save additional data to a Pd patch, using precisely this feature to
re-access it on load.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2008-08-04 19:01
Message:
Logged In: YES
user_id=569446
Originator: YES
But as a feature it is rather broken, because the data at the end of the
file is deleted if you save the patch from Pd. And even the feature can be
build in Pd itself with a loadbang'd semicolon-message box, as matju
pointed out here:
http://lists.puredata.info/pipermail/pd-list/2006-10/043171.html
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 18:45
Message:
Logged In: YES
user_id=564396
Originator: NO
i think this is a feature
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&group_…
Bugs item #1577739, was opened at 2006-10-15 20:42
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&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: 5
Private: No
Submitted By: Frank Barknecht (fbar)
Assigned to: Miller Puckette (millerpuckette)
Summary: Malformed data at end of patch is treated as sender
Initial Comment:
When opening a patch file Pd doesn't check correctly if
all messages are well-formed. Inserting a line at end
of a patch file, that starts with a symbol and ends
with a ";" will treat the leading symbol as a
receive-target and will send the rest of the line to
that receiver.
For example inserting:
pd dsp 1;
at the end of a patch will switch on audio, even when
the patch is started with "pd -noloadbang".
While this message is harmless, other messages may do
nasty things and open a security hole.
Attached is a patch that illustrates this behaviour,
also see this pd-list message thread:
http://lists.puredata.info/pipermail/pd-list/2006-10/043161.html
----------------------------------------------------------------------
>Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 19:44
Message:
Logged In: YES
user_id=564396
Originator: NO
even if matju thinks you can use [loadbang] for these kind of things, he
might be wrong here.
the sent messages are sent immediately (even before a hypothetic
[initbang] message!), whereas the loadbang is delayed rather long. (as we
all now)
as claude has pointed out, the "freer than max" talk should show (i hope)
that you can really do cool things with this additional data, which you
could not do with any other "elegant" method i know.
if objects forget about these messages it is rather broken objects than a
bug in Pd.
(e.g. the FTM-objects happily save (and recall) the data via this
send-"hack")
----------------------------------------------------------------------
Comment By: ClaudiusMaximus (claudiusmaximus)
Date: 2008-08-04 19:18
Message:
Logged In: YES
user_id=769033
Originator: NO
I think it is a feature too - if I recall correctly, the "Freer Than Max:
Porting FTM to Pure-data" presentation at LAC showed that externals can
save additional data to a Pd patch, using precisely this feature to
re-access it on load.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2008-08-04 19:01
Message:
Logged In: YES
user_id=569446
Originator: YES
But as a feature it is rather broken, because the data at the end of the
file is deleted if you save the patch from Pd. And even the feature can be
build in Pd itself with a loadbang'd semicolon-message box, as matju
pointed out here:
http://lists.puredata.info/pipermail/pd-list/2006-10/043171.html
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 18:45
Message:
Logged In: YES
user_id=564396
Originator: NO
i think this is a feature
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&group_…
Bugs item #1577739, was opened at 2006-10-15 18:42
Message generated for change (Comment added) made by claudiusmaximus
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&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: 5
Private: No
Submitted By: Frank Barknecht (fbar)
Assigned to: Miller Puckette (millerpuckette)
Summary: Malformed data at end of patch is treated as sender
Initial Comment:
When opening a patch file Pd doesn't check correctly if
all messages are well-formed. Inserting a line at end
of a patch file, that starts with a symbol and ends
with a ";" will treat the leading symbol as a
receive-target and will send the rest of the line to
that receiver.
For example inserting:
pd dsp 1;
at the end of a patch will switch on audio, even when
the patch is started with "pd -noloadbang".
While this message is harmless, other messages may do
nasty things and open a security hole.
Attached is a patch that illustrates this behaviour,
also see this pd-list message thread:
http://lists.puredata.info/pipermail/pd-list/2006-10/043161.html
----------------------------------------------------------------------
Comment By: ClaudiusMaximus (claudiusmaximus)
Date: 2008-08-04 17:18
Message:
Logged In: YES
user_id=769033
Originator: NO
I think it is a feature too - if I recall correctly, the "Freer Than Max:
Porting FTM to Pure-data" presentation at LAC showed that externals can
save additional data to a Pd patch, using precisely this feature to
re-access it on load.
----------------------------------------------------------------------
Comment By: Frank Barknecht (fbar)
Date: 2008-08-04 17:01
Message:
Logged In: YES
user_id=569446
Originator: YES
But as a feature it is rather broken, because the data at the end of the
file is deleted if you save the patch from Pd. And even the feature can be
build in Pd itself with a loadbang'd semicolon-message box, as matju
pointed out here:
http://lists.puredata.info/pipermail/pd-list/2006-10/043171.html
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 16:45
Message:
Logged In: YES
user_id=564396
Originator: NO
i think this is a feature
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&group_…
Bugs item #1577739, was opened at 2006-10-15 20:42
Message generated for change (Comment added) made by fbar
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&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: 5
Private: No
Submitted By: Frank Barknecht (fbar)
Assigned to: Miller Puckette (millerpuckette)
Summary: Malformed data at end of patch is treated as sender
Initial Comment:
When opening a patch file Pd doesn't check correctly if
all messages are well-formed. Inserting a line at end
of a patch file, that starts with a symbol and ends
with a ";" will treat the leading symbol as a
receive-target and will send the rest of the line to
that receiver.
For example inserting:
pd dsp 1;
at the end of a patch will switch on audio, even when
the patch is started with "pd -noloadbang".
While this message is harmless, other messages may do
nasty things and open a security hole.
Attached is a patch that illustrates this behaviour,
also see this pd-list message thread:
http://lists.puredata.info/pipermail/pd-list/2006-10/043161.html
----------------------------------------------------------------------
>Comment By: Frank Barknecht (fbar)
Date: 2008-08-04 19:01
Message:
Logged In: YES
user_id=569446
Originator: YES
But as a feature it is rather broken, because the data at the end of the
file is deleted if you save the patch from Pd. And even the feature can be
build in Pd itself with a loadbang'd semicolon-message box, as matju
pointed out here:
http://lists.puredata.info/pipermail/pd-list/2006-10/043171.html
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 18:45
Message:
Logged In: YES
user_id=564396
Originator: NO
i think this is a feature
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&group_…
Bugs item #1577739, was opened at 2006-10-15 20:42
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&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: 5
Private: No
Submitted By: Frank Barknecht (fbar)
Assigned to: Miller Puckette (millerpuckette)
Summary: Malformed data at end of patch is treated as sender
Initial Comment:
When opening a patch file Pd doesn't check correctly if
all messages are well-formed. Inserting a line at end
of a patch file, that starts with a symbol and ends
with a ";" will treat the leading symbol as a
receive-target and will send the rest of the line to
that receiver.
For example inserting:
pd dsp 1;
at the end of a patch will switch on audio, even when
the patch is started with "pd -noloadbang".
While this message is harmless, other messages may do
nasty things and open a security hole.
Attached is a patch that illustrates this behaviour,
also see this pd-list message thread:
http://lists.puredata.info/pipermail/pd-list/2006-10/043161.html
----------------------------------------------------------------------
>Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 18:45
Message:
Logged In: YES
user_id=564396
Originator: NO
i think this is a feature
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1577739&group_…
Bugs item #1655662, was opened at 2007-02-09 01:54
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1655662&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.2
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: Matteo Sisti Sette (sistisette)
Assigned to: Nobody/Anonymous (nobody)
Summary: .xa10120: no such object
Initial Comment:
Hi,
This seems to happen under "random" circumstances. It happened to me with every kind of patches (simple and complex) and usually NOT in a sistematic manner (that is, the same patch which once triggers the bug, after restarting PD never does again...)
However, this patch that I attach does sistematically make this happen, at least to me under Windows XP.
The following error message appears in the output window:
>> .xa10120: no such object
This particular patch uses "scripting", i.e. it creates and deletes an object in a subpatch iteratively; however, I saw this same bug happen a lot of times with patches which didn't make any use of scripting at all. I attach this just because it is the only one I have that is sure to trigger the bug.
Sorry I can't "isolate" it further.
Matteo Sisti Sette
----------------------------------------------------------------------
>Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-04 18:25
Message:
Logged In: YES
user_id=564396
Originator: NO
shall we close this and re-open it whenever the bug occurs again?
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2008-05-09 21:59
Message:
Logged In: YES
user_id=27104
Originator: NO
I couldn't reproduce this on Windows XP SP2 with Pd-extended
0.40.3-20080504
----------------------------------------------------------------------
Comment By: Matteo Sisti Sette (sistisette)
Date: 2007-04-23 13:42
Message:
Logged In: YES
user_id=1709568
Originator: YES
I guess it may be windows-specific.
I am reproducing it right now with 0.40-2 vanilla on Windows XP.
Can anyone else reproduce it in windows?
(does anyone else use windows?)
Please note that it is NOT in ANY WAY specific to dinamically creating
patches or objects in patches. It happens to me a lot every day working
with patches that never do anything dynamically and that don't use dyn (nor
any external for what it's worth).
However, here is a typical situation which triggers the bug in my everyday
life:
-work with some rather "big" patch which uses a lot of abstractions (which
I did myself), including a some of them used more than once i.e. a few
instances of the same abstraction; and abstractions contain other
abstractions and so on (no weird infinite loop or anything, just a bit
complex)
-open (with file/open) separately the file of an abstraction which is
being used in the main patch (or inside some other abstraction used in the
main patch etc), edit and save it.
This will for some reason automatically open and close all patch windows
which contain occurences of the saved abstraction (which is quite slow and
quite annoying but is better than older versions which used to open them
without closing), AND produce the mentioned error message.
When this happen, I'm not sure whether the stability and correct behaviour
of PD is compromised, so I usually restart it.
Note however that this is a lot different from the situation exemplified
by the attached patch, and both trigger the bug.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2007-04-23 11:47
Message:
Logged In: NO
I haven't been able to reproduce the problem on win32 pd vanilla 0.40-2,
but,
I've had this problem a lot of time on win32, it always happen when I
create patches dynamically, after an amount of created(/destroyed) patches,
the object maker isn't able to make any new object and send these tk path
names error messages.
Sometimes the tk binding become erroneous within this problem, yesterday
when the bug occured, the Font Bomb windows was opened with clicking on
'FileMenu' button, Media Settings on 'Cancel' button, and SavePanel on 'Ok'
button
But I haven't been able to determine if this is caused by an external or
not.
The problem also occur when the patches are created with the [dyn~]
external.
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-04-23 11:18
Message:
Logged In: YES
user_id=1658640
Originator: NO
I can not reproduce it either on OS X using vanilla 0.40-2 and extended
0.39.2 test7 and RC1. Increaseing the number in the msg does noet seam to
provoke the error either.
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2007-04-23 11:04
Message:
Logged In: YES
user_id=564396
Originator: NO
unfortunately i cannot reproduce this with your patch on linux with
pd-0.39-2 (vanilla) and pd-0.40-1 (vanilla).
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1655662&group_…
Bugs item #1930436, was opened at 2008-03-31 20:51
Message generated for change (Settings changed) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1930436&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: externals
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Hans-Christoph Steiner (eighthave)
Summary: [import pddp/pddplink] prevents loading of [pddp/pddplink]
Initial Comment:
I am using import to load a single external, for example [import pddp/pddplink].
doing so, I can create pddplink without the prefix pddp in my patch.
the only problem is, that [pddp/pddplink] will not work anymore after that. so import breaks existing paths somehow.
I figured out that not using import at all, only [pddp/pddplink] does what I need, because having an object [pddp/pddplink] in a patch will enable [pddplink] if it is created afterwards and [pddp/pddplink] will still work too.
m.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2008-05-18 21:27
Message:
Logged In: YES
user_id=27104
Originator: NO
this still happens on Pd-extended 0.40.3-20080517, attached example patch.
File Added: import_objectclass_bug.pd
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1930436&group_…