#41641 [Bgs->Opn]: Indirect Modification Notice due to modification using __set

2007-08-21 Thread asnyder at mddev dot com
ID: 41641 User updated by: asnyder at mddev dot com Reported By: asnyder at mddev dot com -Status: Bogus +Status: Open -Bug Type: Documentation problem +Bug Type: Scripting Engine problem Operating System: Linux Fedora Core 4 PHP Version

#41641 [Bgs->Opn]: Indirect Modification Notice due to modification using __set

2007-06-25 Thread asnyder at mddev dot com
ID: 41641 User updated by: asnyder at mddev dot com Reported By: asnyder at mddev dot com -Status: Bogus +Status: Open Bug Type: Scripting Engine problem Operating System: Linux Fedora Core 4 PHP Version: 5.2.3 New Comment: Ok, HOW is

#41641 [Bgs->Opn]: Indirect Modification Notice due to modification using __set

2007-06-25 Thread asnyder at mddev dot com
ID: 41641 User updated by: asnyder at mddev dot com Reported By: asnyder at mddev dot com -Status: Bogus +Status: Open Bug Type: Scripting Engine problem Operating System: Linux Fedora Core 4 PHP Version: 5.2.3 New Comment: But it DOES

#41641 [Bgs->Opn]: Indirect Modification Notice due to modification using __set

2007-06-11 Thread asnyder at mddev dot com
ID: 41641 User updated by: asnyder at mddev dot com Reported By: asnyder at mddev dot com -Status: Bogus +Status: Open Bug Type: Scripting Engine problem Operating System: Linux Fedora Core 4 PHP Version: 5.2.3 New Comment: How is this

#41641 [NEW]: Indirect Modification Notice due to modification using __set

2007-06-08 Thread asnyder at mddev dot com
From: asnyder at mddev dot com Operating system: Linux Fedora Core 4 PHP version: 5.2.3 PHP Bug Type: Scripting Engine problem Bug description: Indirect Modification Notice due to modification using __set Description: Ok, the bug is as follows. If one gets an

#33363 [Bgs->Opn]: Crash When memory_get_usage reaches 4868856

2005-06-16 Thread asnyder at mddev dot com
ID: 33363 User updated by: asnyder at mddev dot com Reported By: asnyder at mddev dot com -Status: Bogus +Status: Open Bug Type: Reproducible crash Operating System: Linux Fedora PHP Version: 4.3.10 New Comment: This is not a bogus bug

#33363 [Bgs]: Crash When memory_get_usage reaches 4868856

2005-06-16 Thread asnyder at mddev dot com
ID: 33363 User updated by: asnyder at mddev dot com Reported By: asnyder at mddev dot com Status: Bogus Bug Type: Reproducible crash Operating System: Linux Fedora PHP Version: 4.3.10 New Comment: Our usual consultant pay is 25/hr. Previous

#33363 [Bgs]: Crash When memory_get_usage reaches 4868856

2005-06-16 Thread asnyder at mddev dot com
ID: 33363 User updated by: asnyder at mddev dot com Reported By: asnyder at mddev dot com Status: Bogus Bug Type: Reproducible crash Operating System: Linux Fedora PHP Version: 4.3.10 New Comment: I'm trying my best to explain. if I we

#33363 [Fbk->Opn]: Crash When memory_get_usage reaches 4868856

2005-06-16 Thread asnyder at mddev dot com
ID: 33363 User updated by: asnyder at mddev dot com Reported By: asnyder at mddev dot com -Status: Feedback +Status: Open Bug Type: Reproducible crash Operating System: Linux Fedora PHP Version: 4.3.10 New Comment: Unfortunately, there

#33363 [NEW]: Crash When memory_get_usage reaches 4868856

2005-06-16 Thread asnyder at mddev dot com
From: asnyder at mddev dot com Operating system: Linux Fedora PHP version: 4.3.10 PHP Bug Type: Reproducible crash Bug description: Crash When memory_get_usage reaches 4868856 Description: Here's the problem in the nutshell. For whatever reason a