nick rothwell | project cassiel

> Provide a descriptive summary of the issue.

> In numbered format, detail the exact steps taken to produce the bug.

i. create a filedrop object in a new patcher

ii. send the message 'types #1' to the filedrop

iii. save the patcher (I'm saving as text, FWIW)

iv. try to use this patcher inside a bpatcher

v. bang, illegal address exception (null) inside filedrop

> Describe what you expected to happen when you executed the steps 

> Please explain what actually occurred when steps above are executed.

> Describe circumstances where the problem occurs or does not occur,

> such as software versions and/or hardware configurations.

Problem occurs on MaxMSP 4.5.7, OS X 10.4.6.

> Provide additional information, such as references to related

> problems, workarounds and relevant attachments.

Why does filedrop save its current 'types' configuration in the 

patcher? This behaviour is not visible (filedrop doesn't have an 

nick rothwell -- composition, systems, performance -- 

> Summary:
 > Provide a descriptive summary of the issue.

 > Steps to Reproduce:
 > In numbered format, detail the exact steps taken to produce the bug.

i. create a filedrop object in a new patcher
ii. send the message 'types #1' to the filedrop
iii. save the patcher (I'm saving as text, FWIW)
iv. try to use this patcher inside a bpatcher
v. bang, illegal address exception (null) inside filedrop

 > Expected Results:
 > Describe what you expected to happen when you executed the steps  
above.

 > Actual Results:
 > Please explain what actually occurred when steps above are executed.

 > Regression:
 > Describe circumstances where the problem occurs or does not occur,
 > such as software versions and/or hardware configurations.

 > Notes:
 > Provide additional information, such as references to related
 > problems, workarounds and relevant attachments.

Why does filedrop save its current 'types' configuration in the  
patcher? This behaviour is not visible (filedrop doesn't have an  
inspector).

   nick rothwell -- composition, systems, performance -- http:// 
www.cassiel.com


bug-report-how-to-byork-and-crash-filedrop

On 11 May 2006, at 16:23, Nick Rothwell wrote:

> > Provide a descriptive summary of the issue.

Rothwell refers to "dropfile" as "filedrop".

Rothwell should pay more attention in class.

> > Summary:
> > Provide a descriptive summary of the issue.

> > > Provide a descriptive summary of the issue.

> Rothwell refers to "dropfile" as "filedrop".

> > > Summary:
> > > Provide a descriptive summary of the issue.
>
> Rothwell refers to "dropfile" as "filedrop".

Bug report: how to byork and crash filedrop