From metatracker at psf.upfronthosting.co.za Sat Oct 10 18:06:32 2009 From: metatracker at psf.upfronthosting.co.za (Ronald Oussoren) Date: Sat, 10 Oct 2009 16:06:32 +0000 Subject: [Tracker-discuss] [issue302] make 'closed' issues read-only In-Reply-To: <1255190792.01.0.359829287099.issue302@psf.upfronthosting.co.za> Message-ID: <1255190792.01.0.359829287099.issue302@psf.upfronthosting.co.za> New submission from Ronald Oussoren : I've noticed several time in the patch that users add new unrelated information to issues that are already closed, instead of opening a new issue. This is unhelpful because the new issue might go unnoticed, and because it mudles the news file. That is, if a news file notes "Fixes issue 1234" it is not immediately clear if this refers to the original issue or the new message added to the end of an already resolved one. I would therefore prefer if issues were read-only once closed, but probably not for developers in the "Assigned to:" list and also not for people on the nosy list. ---------- messages: 1476 nosy: ronaldoussoren priority: wish status: unread title: make 'closed' issues read-only _______________________________________________________ PSF Meta Tracker _______________________________________________________ From rdmurray at bitdance.com Sat Oct 10 18:29:22 2009 From: rdmurray at bitdance.com (R. David Murray) Date: Sat, 10 Oct 2009 12:29:22 -0400 (EDT) Subject: [Tracker-discuss] [issue302] make 'closed' issues read-only In-Reply-To: <1255190792.01.0.359829287099.issue302@psf.upfronthosting.co.za> References: <1255190792.01.0.359829287099.issue302@psf.upfronthosting.co.za> Message-ID: On Sat, 10 Oct 2009 at 16:06, Ronald Oussoren wrote: > I've noticed several time in the patch that users add new unrelated information > to issues that are already closed, instead of opening a new issue. > > This is unhelpful because the new issue might go unnoticed, and because it This is true. Some bug trackers auto-open an issue when new information is added. I'm not sure that this is a good idea, but it is a option. > mudles the news file. That is, if a news file notes "Fixes issue 1234" it is not > immediately clear if this refers to the original issue or the new message added > to the end of an already resolved one. If the committer follows the convention of noting the revision in which the fix was committed, then it is pretty clear from scanning the issue what was fixed (that is, anything after the message giving the commit info was _not_ dealt with). > I would therefore prefer if issues were read-only once closed, but probably not > for developers in the "Assigned to:" list and also not for people on the nosy > list. I don't think I've run into any other bug tracker that works this way, and I'm not sure it is a good idea. Specifically, if someone other than the interested parties discovers that the fix did not work (perhaps on a platform the original parties did not test on), or caused a new problem, then the original issue is usually the appropriate place to report it (and those on the nosy list will get notified, which mitigates the "closed issue not noticed" problem). --David (RDM) From metatracker at psf.upfronthosting.co.za Sat Oct 10 18:29:29 2009 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Sat, 10 Oct 2009 16:29:29 +0000 Subject: [Tracker-discuss] [issue302] make 'closed' issues read-only In-Reply-To: <1255190792.01.0.359829287099.issue302@psf.upfronthosting.co.za> Message-ID: R David Murray added the comment: On Sat, 10 Oct 2009 at 16:06, Ronald Oussoren wrote: > I've noticed several time in the patch that users add new unrelated information > to issues that are already closed, instead of opening a new issue. > > This is unhelpful because the new issue might go unnoticed, and because it This is true. Some bug trackers auto-open an issue when new information is added. I'm not sure that this is a good idea, but it is a option. > mudles the news file. That is, if a news file notes "Fixes issue 1234" it is not > immediately clear if this refers to the original issue or the new message added > to the end of an already resolved one. If the committer follows the convention of noting the revision in which the fix was committed, then it is pretty clear from scanning the issue what was fixed (that is, anything after the message giving the commit info was _not_ dealt with). > I would therefore prefer if issues were read-only once closed, but probably not > for developers in the "Assigned to:" list and also not for people on the nosy > list. I don't think I've run into any other bug tracker that works this way, and I'm not sure it is a good idea. Specifically, if someone other than the interested parties discovers that the fix did not work (perhaps on a platform the original parties did not test on), or caused a new problem, then the original issue is usually the appropriate place to report it (and those on the nosy list will get notified, which mitigates the "closed issue not noticed" problem). --David (RDM) ---------- nosy: +r.david.murray status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Oct 11 13:30:02 2009 From: metatracker at psf.upfronthosting.co.za (Ronald Oussoren) Date: Sun, 11 Oct 2009 11:30:02 +0000 Subject: [Tracker-discuss] [issue302] make 'closed' issues read-only In-Reply-To: <1255190792.01.0.359829287099.issue302@psf.upfronthosting.co.za> Message-ID: <1255260602.13.0.102678796759.issue302@psf.upfronthosting.co.za> Ronald Oussoren added the comment: David: the nosy list only helps if those on the list actually react to the nosy message. I often use the e-mail I get from the tracker as a warning that something needs to be done and don't react immediately unless the issue seems very critical. I then use the one of the report on bugs.python.org to check for issues that are interesting for me (assigned to me, I'm on the nosy list, ...). Those reports do not include issues that are closed, which means that additional messages to an already closed issue tend to get ignored. W.r.t. mudling the news file, I meant Misc/NEWS in Python's distribution. That contains longish lists of "Fixes issue #1234: foobar crashes the interpreter", where the part after the colon is often the title of the issue. If a new message to closed issue #1234 results in a new bugfix you'll get a second "Fixes issue #1234" line in a later release of python, which is fine if issue #1234 wasn't fixed after all but is confusing if the new message was an unrelated issue. The reason I wrote this wish is that I have had to ask several users to open a new issue because the added a message to an already closed issue, and the new message was only slightly related to the issue at hand. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Oct 11 14:02:23 2009 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Sun, 11 Oct 2009 12:02:23 +0000 Subject: [Tracker-discuss] [issue302] make 'closed' issues read-only In-Reply-To: <1255190792.01.0.359829287099.issue302@psf.upfronthosting.co.za> Message-ID: <1255262543.8.0.44077312443.issue302@psf.upfronthosting.co.za> Martin v. L?wis added the comment: FWIW, the SF tracker (now) has a feature "Close posting" with a check-box that gets auto-checked when you select the Close status (it didn't have that feature when we were still using it). I don't like the feature very much, since I now get personal email as follow-up from people who can't post to the original issue anymore; I also get new issues that start with "this is a follow-up to XYZ which is closed". So I agree with David that closing posting is inappropriate in general. I'm not sure whether Ronald's proposal of allowing people on the nosy list to follow- up would soften the problem. It may, but then people may also learn that they just have to add themselves to the nosy list, and complain about this "stupid restriction". The standard roundup template has an auto-reopen feature (on follow-ups); I don't like it since messages like "thanks for fixing it" did cause reopens quite often in this specific tracker (which uses the standard roundup template). As a compromise, how about posting a bold and/or red-colored text on the submit form if the current status is "closed"? Even stronger (but more difficult to implement) would be an initial replacement of the Change Note form with a button "I understand that the issue is closed but want to post on it, anyway"; the actual input field would only appear after selecting this button. ---------- nosy: +loewis _______________________________________________________ PSF Meta Tracker _______________________________________________________ From rdmurray at bitdance.com Sun Oct 11 22:39:07 2009 From: rdmurray at bitdance.com (R. David Murray) Date: Sun, 11 Oct 2009 16:39:07 -0400 (EDT) Subject: [Tracker-discuss] [issue302] make 'closed' issues read-only In-Reply-To: <1255260602.13.0.102678796759.issue302@psf.upfronthosting.co.za> References: <1255260602.13.0.102678796759.issue302@psf.upfronthosting.co.za> Message-ID: On Sun, 11 Oct 2009 at 11:30, Ronald Oussoren wrote: > W.r.t. mudling the news file, I meant Misc/NEWS in Python's distribution. That > contains longish lists of "Fixes issue #1234: foobar crashes the interpreter", > where the part after the colon is often the title of the issue. If a new message > to closed issue #1234 results in a new bugfix you'll get a second "Fixes issue > #1234" line in a later release of python, which is fine if issue #1234 wasn't > fixed after all but is confusing if the new message was an unrelated issue. I don't think we should ever have a second "fixes #xxxx" in NEWS. If a committer seems to be in the position of needing to do that (ie: it was fixed in release X but the fix needs patching in release X+1), what they need to do instead is open a new bug, even if the person who effectively reopened the closed bug hasn't done so themselves. > The reason I wrote this wish is that I have had to ask several users to open a > new issue because the added a message to an already closed issue, and the new > message was only slightly related to the issue at hand. Yeah. I'm afraid that just comes with the job, though :) If there were more people triaging bugs you might not have to do it yourself. I like Martin's suggestion of an "are you really sure?" button. That might help a lot without preventing people from making legitimate comments closed bugs. --David (RDM) From metatracker at psf.upfronthosting.co.za Sun Oct 11 22:39:12 2009 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Sun, 11 Oct 2009 20:39:12 +0000 Subject: [Tracker-discuss] [issue302] make 'closed' issues read-only In-Reply-To: <1255260602.13.0.102678796759.issue302@psf.upfronthosting.co.za> Message-ID: R David Murray added the comment: On Sun, 11 Oct 2009 at 11:30, Ronald Oussoren wrote: > W.r.t. mudling the news file, I meant Misc/NEWS in Python's distribution. That > contains longish lists of "Fixes issue #1234: foobar crashes the interpreter", > where the part after the colon is often the title of the issue. If a new message > to closed issue #1234 results in a new bugfix you'll get a second "Fixes issue > #1234" line in a later release of python, which is fine if issue #1234 wasn't > fixed after all but is confusing if the new message was an unrelated issue. I don't think we should ever have a second "fixes #xxxx" in NEWS. If a committer seems to be in the position of needing to do that (ie: it was fixed in release X but the fix needs patching in release X+1), what they need to do instead is open a new bug, even if the person who effectively reopened the closed bug hasn't done so themselves. > The reason I wrote this wish is that I have had to ask several users to open a > new issue because the added a message to an already closed issue, and the new > message was only slightly related to the issue at hand. Yeah. I'm afraid that just comes with the job, though :) If there were more people triaging bugs you might not have to do it yourself. I like Martin's suggestion of an "are you really sure?" button. That might help a lot without preventing people from making legitimate comments closed bugs. --David (RDM) _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Oct 16 12:27:01 2009 From: metatracker at psf.upfronthosting.co.za (Marc-Andre Lemburg) Date: Fri, 16 Oct 2009 10:27:01 +0000 Subject: [Tracker-discuss] [issue303] Exception when sending a ticket reply via email In-Reply-To: <1255688821.53.0.717488738607.issue303@psf.upfronthosting.co.za> Message-ID: <1255688821.53.0.717488738607.issue303@psf.upfronthosting.co.za> New submission from Marc-Andre Lemburg : Email replies don't appear to work anymore: This is the mail system at host psf.upfronthosting.co.za. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): Command died with status 1: "/home/roundup/roundup/bin/roundup-mailgw /home/roundup/trackers/tracker". Command output: Traceback (most recent call last): File "/home/roundup/roundup/bin/roundup-mailgw", line 6, in ? run() File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/scripts/roundup_mailgw.py", line 210, in run sys.exit(main(sys.argv)) File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/scripts/roundup_mailgw.py", line 153, in main return handler.do_pipe() File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/mailgw.py", line 554, in do_pipe self.main(s) File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/mailgw.py", line 716, in main return self.handle_Message(Message(fp)) File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/mailgw.py", line 768, in handle_Message self.mailer.bounce_message(message, [sendto[0][1]], m) File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/mailer.py", line 151, in bounce_message part = MIMEText(error) File "email/MIMEText.py", line 28, in __init__ File "email/Message.py", line 218, in set_payload File "email/Message.py", line 258, in set_charset File "email/Encoders.py", line 63, in encode_7or8bit AttributeError: 'list' object has no attribute 'encode' Reporting-MTA: dns; psf.upfronthosting.co.za X-Postfix-Queue-ID: A51767803E X-Postfix-Sender: rfc822; mal at egenix.com Arrival-Date: Fri, 16 Oct 2009 12:20:48 +0200 (CEST) Final-Recipient: rfc822; roundup+tracker at psf.upfronthosting.co.za Original-Recipient: rfc822;report at bugs.python.org Action: failed Status: 5.3.0 Diagnostic-Code: x-unix; Traceback (most recent call last): File "/home/roundup/roundup/bin/roundup-mailgw", line 6, in ? run() File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/scripts/roundup_mailgw.py", line 210, in run sys.exit(main(sys.argv)) File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/scripts/roundup_mailgw.py", line 153, in main return handler.do_pipe() File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/mailgw.py", line 554, in do_pipe self.main(s) File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/mailgw.py", line 716, in main return self.handle_Message(Message(fp)) File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/mailgw.py", line 768, in handle_Message self.mailer.bounce_message(message, [sendto[0][1]], m) File "/home/roundup/roundup/lib/python2.4/site-packages/roundup/mailer.py", line 151, in bounce_message part = MIMEText(error) File "email/MIMEText.py", line 28, in __init__ File "email/Message.py", line 218, in set_payload File "email/Message.py", line 258, in set_charset File "email/Encoders.py", line 63, in encode_7or8bit AttributeError: 'list' object has no attribute 'encode' ---------- messages: 1481 nosy: lemburg priority: urgent status: unread title: Exception when sending a ticket reply via email _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Oct 29 14:35:16 2009 From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou) Date: Thu, 29 Oct 2009 13:35:16 +0000 Subject: [Tracker-discuss] [issue304] Display of HTTP URLs is borked. In-Reply-To: <1256823316.36.0.698718751835.issue304@psf.upfronthosting.co.za> Message-ID: <1256823316.36.0.698718751835.issue304@psf.upfronthosting.co.za> New submission from Antoine Pitrou : Example: http://bugs.python.org/msg94667 ---------- messages: 1482 nosy: pitrou priority: bug status: unread title: Display of HTTP URLs is borked. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Oct 29 18:51:31 2009 From: metatracker at psf.upfronthosting.co.za (MN) Date: Thu, 29 Oct 2009 17:51:31 +0000 Subject: [Tracker-discuss] [issue306] Error when running a code In-Reply-To: <1256838691.6.0.0592951773269.issue306@psf.upfronthosting.co.za> Message-ID: <1256838691.6.0.0592951773269.issue306@psf.upfronthosting.co.za> New submission from MN : Process: Python [12147] Path: /Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python Identifier: org.python.python Version: 2.6.2 (2.6.2) Code Type: X86 (Native) Parent Process: Python [11727] Date/Time: 2009-10-29 16:43:59.064 +0000 OS Version: Mac OS X 10.6.1 (10B504) Report Version: 6 Interval Since Last Report: 60085 sec Crashes Since Last Report: 3 Per-App Interval Since Last Report: 8 sec Per-App Crashes Since Last Report: 2 Anonymous UUID: 2FD60074-C28B-48E1-AB01-5A5B2E3B28D3 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Crashed Thread: 4 Application Specific Information: abort() called Thread 0: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x948df822 semaphore_wait_signal_trap + 10 1 libSystem.B.dylib 0x9490d3d8 _pthread_cond_wait + 1089 2 libSystem.B.dylib 0x9495670f pthread_cond_wait + 48 3 org.python.python 0x000e82f5 PyThread_acquire_lock + 140 (thread_pthread.h:454) 4 org.python.python 0x000eca2d lock_PyThread_acquire_lock + 80 (threadmodule.c:46) 5 org.python.python 0x000b44ca PyEval_EvalFrameEx + 20905 (ceval.c:3706) 6 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 7 org.python.python 0x000b2d61 PyEval_EvalFrameEx + 14912 (ceval.c:3802) 8 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 9 org.python.python 0x000b2d61 PyEval_EvalFrameEx + 14912 (ceval.c:3802) 10 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 11 org.python.python 0x000b2d61 PyEval_EvalFrameEx + 14912 (ceval.c:3802) 12 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 13 org.python.python 0x0003b16c function_call + 162 (funcobject.c:524) 14 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 15 org.python.python 0x0001f0b4 instancemethod_call + 401 (classobject.c:2579) 16 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 17 org.python.python 0x000ae4df PyEval_CallObjectWithKeywords + 72 (ceval.c:3575) 18 org.python.python 0x00021b20 PyInstance_New + 114 (classobject.c:568) 19 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 20 org.python.python 0x000b1916 PyEval_EvalFrameEx + 9717 (ceval.c:3917) 21 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 22 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 23 org.python.python 0x000b523d PyEval_EvalFrameEx + 24348 (ceval.c:522) 24 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 25 org.python.python 0x0003b16c function_call + 162 (funcobject.c:524) 26 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 27 org.python.python 0x000b224c PyEval_EvalFrameEx + 12075 (ceval.c:4005) 28 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 29 org.python.python 0x000b2d61 PyEval_EvalFrameEx + 14912 (ceval.c:3802) 30 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 31 org.python.python 0x000b5d42 PyEval_EvalCode + 87 (ceval.c:528) 32 org.python.python 0x000db3af PyRun_StringFlags + 289 (pythonrun.c:1335) 33 org.python.python 0x000db488 PyRun_SimpleStringFlags + 72 (pythonrun.c:957) 34 org.python.python 0x000eaa0d Py_Main + 1378 (main.c:548) 35 org.python.python 0x00001f4e 0x1000 + 3918 36 org.python.python 0x00001e69 0x1000 + 3689 Thread 1: Dispatch queue: com.apple.libdispatch-manager 0 libSystem.B.dylib 0x9490603a kevent + 10 1 libSystem.B.dylib 0x94906768 _dispatch_mgr_invoke + 215 2 libSystem.B.dylib 0x94905bf9 _dispatch_queue_invoke + 183 3 libSystem.B.dylib 0x9490598a _dispatch_worker_thread2 + 234 4 libSystem.B.dylib 0x94905401 _pthread_wqthread + 390 5 libSystem.B.dylib 0x94905246 start_wqthread + 30 Thread 2: 0 libSystem.B.dylib 0x94905092 __workq_kernreturn + 10 1 libSystem.B.dylib 0x94905628 _pthread_wqthread + 941 2 libSystem.B.dylib 0x94905246 start_wqthread + 30 Thread 3: 0 libSystem.B.dylib 0x948df822 semaphore_wait_signal_trap + 10 1 libSystem.B.dylib 0x9490d3d8 _pthread_cond_wait + 1089 2 libSystem.B.dylib 0x9495670f pthread_cond_wait + 48 3 org.python.python 0x000e82f5 PyThread_acquire_lock + 140 (thread_pthread.h:454) 4 org.python.python 0x000ae251 PyEval_RestoreThread + 60 (ceval.c:335) 5 select.so 0x012ed679 select_select + 483 (selectmodule.c:286) 6 org.python.python 0x000b44ca PyEval_EvalFrameEx + 20905 (ceval.c:3706) 7 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 8 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 9 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 10 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 11 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 12 org.python.python 0x0003b16c function_call + 162 (funcobject.c:524) 13 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 14 org.python.python 0x0001f0b4 instancemethod_call + 401 (classobject.c:2579) 15 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 16 org.python.python 0x000b1916 PyEval_EvalFrameEx + 9717 (ceval.c:3917) 17 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 18 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 19 org.python.python 0x0003b16c function_call + 162 (funcobject.c:524) 20 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 21 org.python.python 0x0001f0b4 instancemethod_call + 401 (classobject.c:2579) 22 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 23 org.python.python 0x000b1916 PyEval_EvalFrameEx + 9717 (ceval.c:3917) 24 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 25 org.python.python 0x0003b16c function_call + 162 (funcobject.c:524) 26 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 27 org.python.python 0x0001f0b4 instancemethod_call + 401 (classobject.c:2579) 28 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 29 org.python.python 0x0006ce21 slot_tp_init + 75 (typeobject.c:5632) 30 org.python.python 0x0006b9a6 type_call + 162 (typeobject.c:745) 31 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 32 org.python.python 0x000b1916 PyEval_EvalFrameEx + 9717 (ceval.c:3917) 33 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 34 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 35 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 36 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 37 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 38 org.python.python 0x0003b16c function_call + 162 (funcobject.c:524) 39 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 40 org.python.python 0x000b224c PyEval_EvalFrameEx + 12075 (ceval.c:4005) 41 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 42 org.python.python 0x000b4a4b PyEval_EvalFrameEx + 22314 (ceval.c:3792) 43 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 44 org.python.python 0x0003b16c function_call + 162 (funcobject.c:524) 45 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 46 org.python.python 0x0001f0b4 instancemethod_call + 401 (classobject.c:2579) 47 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 48 org.python.python 0x000ae4df PyEval_CallObjectWithKeywords + 72 (ceval.c:3575) 49 org.python.python 0x000ed089 t_bootstrap + 62 (threadmodule.c:425) 50 libSystem.B.dylib 0x9490cf39 _pthread_start + 345 51 libSystem.B.dylib 0x9490cdbe thread_start + 34 Thread 4 Crashed: 0 libSystem.B.dylib 0x9494cc2e __semwait_signal_nocancel + 10 1 libSystem.B.dylib 0x9494cb12 nanosleep$NOCANCEL$UNIX2003 + 166 2 libSystem.B.dylib 0x949c85a6 usleep$NOCANCEL$UNIX2003 + 61 3 libSystem.B.dylib 0x949e9c5c abort + 105 4 com.tcltk.tcllibrary 0x011664a3 Tcl_Panic + 0 5 com.tcltk.tcllibrary 0x011664be Tcl_Panic + 27 6 com.tcltk.tklibrary 0x0125c215 Tk_MacOSXSetupTkNotifier + 120 7 com.tcltk.tklibrary 0x012526f0 TkpInit + 45 8 com.tcltk.tklibrary 0x011e667a Initialize + 2173 9 _tkinter.so 0x010f575c Tcl_AppInit + 123 (tkappinit.c:81) 10 _tkinter.so 0x010f383b Tkinter_Create + 963 (_tkinter.c:689) 11 org.python.python 0x000b44ca PyEval_EvalFrameEx + 20905 (ceval.c:3706) 12 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 13 org.python.python 0x0003b16c function_call + 162 (funcobject.c:524) 14 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 15 org.python.python 0x0001f0b4 instancemethod_call + 401 (classobject.c:2579) 16 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 17 org.python.python 0x000ae4df PyEval_CallObjectWithKeywords + 72 (ceval.c:3575) 18 org.python.python 0x00021b20 PyInstance_New + 114 (classobject.c:568) 19 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 20 org.python.python 0x000b1916 PyEval_EvalFrameEx + 9717 (ceval.c:3917) 21 org.python.python 0x000b5b8b PyEval_EvalCodeEx + 1967 (ceval.c:2968) 22 org.python.python 0x0003b16c function_call + 162 (funcobject.c:524) 23 org.python.python 0x0000ecaa PyObject_Call + 77 (abstract.c:2492) 24 org.python.python 0x000ae4df PyEval_CallObjectWithKeywords + 72 (ceval.c:3575) 25 org.python.python 0x000ed089 t_bootstrap + 62 (threadmodule.c:425) 26 libSystem.B.dylib 0x9490cf39 _pthread_start + 345 27 libSystem.B.dylib 0x9490cdbe thread_start + 34 Thread 4 crashed with X86 Thread State (32-bit): eax: 0x0000003c ebx: 0x9494ca79 ecx: 0xb020557c edx: 0x9494cc2e edi: 0x2f317e35 esi: 0xb02055d8 ebp: 0xb02055b8 esp: 0xb020557c ss: 0x0000001f efl: 0x00000247 eip: 0x9494cc2e cs: 0x00000007 ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037 cr2: 0x02069010 Binary Images: 0x1000 - 0x1fff +org.python.python 2.6.2 (2.6.2) /Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python 0x5000 - 0x120fc3 +org.python.python 2.6.2, (c) 2004-2008 Python Software Foundation. (2.6.2) /Library/Frameworks/Python.framework/Versions/2.6/Python 0x4e8000 - 0x4e9ffb +time.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/time.so 0x4f4000 - 0x4f5fff +cStringIO.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/cStringIO.so 0x640000 - 0x646ffb +_socket.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_socket.so 0x69d000 - 0x6a0ffb +_ssl.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_ssl.so 0x6b4000 - 0x6dafff libssl.0.9.7.dylib ??? (???) <8BF98B2F-0F55-40CA-C082-43C76707BD24> /usr/lib/libssl.0.9.7.dylib 0x6e9000 - 0x79efe7 libcrypto.0.9.7.dylib ??? (???) <4917E4F2-817F-5AC4-3FBE-54BC96360448> /usr/lib/libcrypto.0.9.7.dylib 0x7e4000 - 0x7e4fff +_functools.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_functools.so 0x7eb000 - 0x7eefff +_collections.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_collections.so 0x1000000 - 0x1002fff +operator.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/operator.so 0x100e000 - 0x1012fff +itertools.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/itertools.so 0x1027000 - 0x1027ffc +_bisect.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_bisect.so 0x102e000 - 0x102ffff +_heapq.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_heapq.so 0x10ef000 - 0x10f5fff +_tkinter.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_tkinter.so 0x110a000 - 0x119bfe7 com.tcltk.tcllibrary 8.4.19 (8.4.19) <6FF5C975-96BA-3370-AD5D-AAE625BE5D9A> /System/Library/Frameworks/Tcl.framework/Versions/8.4/Tcl 0x11b9000 - 0x1283fe7 com.tcltk.tklibrary 8.4.19 (8.4.19) <4F15559E-41DD-54A7-81DC-216B5B743401> /System/Library/Frameworks/Tk.framework/Versions/8.4/Tk 0x12db000 - 0x12defff +strop.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/strop.so 0x12eb000 - 0x12edfff +select.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/select.so 0x1740000 - 0x1743ffb +_struct.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_struct.so 0x1754000 - 0x1761ff7 +cPickle.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/cPickle.so 0x17c0000 - 0x17c2ff3 +math.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/math.so 0x17cd000 - 0x17d1fff +binascii.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/binascii.so 0x17db000 - 0x17dcff3 +_random.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_random.so 0x17e4000 - 0x17e5fff +fcntl.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/fcntl.so 0x17ed000 - 0x17eefff +_locale.so ??? (???) /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_locale.so 0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <211AF0DD-42D9-79C8-BB6A-1F4BEEF4B4AB> /usr/lib/dyld 0x90114000 - 0x9011dff7 com.apple.DiskArbitration 2.3 (2.3) /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x9011e000 - 0x90164ff7 libauto.dylib ??? (???) /usr/lib/libauto.dylib 0x90165000 - 0x901a8ff7 com.apple.NavigationServices 3.5.3 (181) <28CDD978-030E-7D4A-5334-874A8EBE6C29> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices 0x90717000 - 0x9077bffb com.apple.htmlrendering 72 (1.1.4) <4D451A35-FAB6-1288-71F6-F24A4B6E2371> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering 0x907c6000 - 0x907d3ff7 com.apple.NetFS 3.2 (3.2) /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x907d4000 - 0x907deff7 libCSync.A.dylib ??? (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib 0x907df000 - 0x907e0ff7 com.apple.TrustEvaluationAgent 1.0 (1) <71E2DA16-83EC-6056-FFEE-862A04B5599F> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0x90838000 - 0x908d5ff3 com.apple.LaunchServices 360.3 (360.3) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x90cf5000 - 0x90cf5ff7 com.apple.Accelerate.vecLib 3.5 (vecLib 3.5) <3E039E14-2A15-56CC-0074-EE59F9FBB913> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x90cf6000 - 0x90d07ff7 com.apple.LangAnalysis 1.6.5 (1.6.5) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0x90d08000 - 0x90d77ff7 libvMisc.dylib ??? (???) <59243A8C-2B98-3E71-8032-884D4853E79F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x90de7000 - 0x90e30fe7 libTIFF.dylib ??? (???) <6EF87001-6FB4-1405-C588-F6D8042D3534> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x90e31000 - 0x90eeafe7 libsqlite3.dylib ??? (???) <16CEF8E8-8C9A-94CD-EF5D-05477844C005> /usr/lib/libsqlite3.dylib 0x90eeb000 - 0x90f3bfe7 libGLU.dylib ??? (???) <55A69DCE-1237-341E-F239-CDFE1F5B19BB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib 0x90f3f000 - 0x90f5dff7 com.apple.CoreVideo 1.6.0 (43.0) <3A853574-DD9E-08D8-FD2C-6221B55C3E08> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo 0x90fa7000 - 0x913dcff7 libLAPACK.dylib ??? (???) <5E2D2283-57DE-9A49-1DB0-CD027FEFA6C2> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x913dd000 - 0x913e1ff7 libGFXShared.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib 0x913e2000 - 0x913e4ff7 libRadiance.dylib ??? (???) <0E03CF64-0931-7B9A-F617-4387B809D6D8> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x91426000 - 0x91527fe7 libxml2.2.dylib ??? (???) /usr/lib/libxml2.2.dylib 0x91688000 - 0x916e8fe7 com.apple.CoreText 3.0.0 (???) <8F4FCAE2-8E6F-F0DE-A6AA-15D0228B7F13> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText 0x916e9000 - 0x916f9ff7 libsasl2.2.dylib ??? (???) /usr/lib/libsasl2.2.dylib 0x916fa000 - 0x916fdff7 libCoreVMClient.dylib ??? (???) <16BB2178-B32D-E57E-F1E4-D177F7754232> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib 0x916fe000 - 0x91703ff7 com.apple.OpenDirectory 10.6 (10.6) <92582807-E8F3-3DD9-EB42-4195CFB754A1> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory 0x91717000 - 0x91809ff7 libcrypto.0.9.8.dylib ??? (???) <792B8722-3091-5E9F-E25F-67499CFE0599> /usr/lib/libcrypto.0.9.8.dylib 0x92802000 - 0x92c18ff7 libBLAS.dylib ??? (???) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x92f14000 - 0x92f18ff7 libGIF.dylib ??? (???) <51848EBF-27D4-0F85-C22A-D1AE10D328F3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x92f19000 - 0x92f31ff7 com.apple.CFOpenDirectory 10.6 (10.6) <1537FB4F-C112-5D12-1E5D-3B1002A4038F> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory 0x92f51000 - 0x9302eff7 com.apple.vImage 4.0 (4.0) <64597E4B-F144-DBB3-F428-0EC3D9A1219E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x930ce000 - 0x930cfff7 com.apple.audio.units.AudioUnit 1.6 (1.6) <68180B96-381C-A09D-5576-606A134FD953> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit 0x930d0000 - 0x931aafff com.apple.DesktopServices 1.5.1 (1.5.1) /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0x93b8b000 - 0x93c23fe7 edu.mit.Kerberos 6.5.8 (6.5.8) /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x93c24000 - 0x93ceefef com.apple.CoreServices.OSServices 352 (352) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x93fc7000 - 0x94237ffb com.apple.Foundation 6.6 (751) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x94238000 - 0x94238ff7 com.apple.CoreServices 44 (44) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x94239000 - 0x9423bff7 com.apple.securityhi 4.0 (36638) <962C66FB-5BE9-634E-0810-036CB340C059> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI 0x9437c000 - 0x943c0fe7 com.apple.Metadata 10.6.0 (507.1) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x943c1000 - 0x9442bfe7 libstdc++.6.dylib ??? (???) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib 0x945fe000 - 0x94780fe7 libicucore.A.dylib ??? (???) /usr/lib/libicucore.A.dylib 0x9488f000 - 0x948c2ff7 com.apple.AE 496 (496) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x948c3000 - 0x948deff7 libPng.dylib ??? (???) <38DD4AA1-0643-85A0-F2F5-EE9269729975> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x948df000 - 0x94a83feb libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib 0x94a86000 - 0x94aa6fe7 libresolv.9.dylib ??? (???) /usr/lib/libresolv.9.dylib 0x94aa7000 - 0x94ae9fe7 libvDSP.dylib ??? (???) <8F8FFFB3-81E3-2969-5688-D5B0979182E6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x952d0000 - 0x953f9fe7 com.apple.audio.toolbox.AudioToolbox 1.6 (1.6) <62BEEBE6-68FC-4A48-91CF-39DA2BD793F1> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox 0x95523000 - 0x9552afff com.apple.print.framework.Print 6.0 (237) <7A06B15C-B835-096E-7D96-C2FE8F0D21E1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x9552b000 - 0x956a2fef com.apple.CoreFoundation 6.6 (550) <193E33D6-2E92-3452-773B-60A1A9CCC573> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x956c1000 - 0x95712ff7 com.apple.HIServices 1.8.0 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x95752000 - 0x957f9fe7 com.apple.CFNetwork 454.4 (454.4) <7C563385-9893-3B48-8607-5BC81DA2C4CF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x95805000 - 0x95b24fe7 com.apple.CoreServices.CarbonCore 859.1 (859.1) <2E72AF56-4BE6-294A-7372-19C360688B8B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x95b25000 - 0x95bd4fef com.apple.ColorSync 4.6.0 (4.6.0) <66ABAE86-B0EC-D641-913D-08ACA965F9FA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x95bd5000 - 0x95c09ff7 libcups.2.dylib ??? (???) <9078BA07-DEE1-6597-D15D-7BE3A20CB5A0> /usr/lib/libcups.2.dylib 0x95c0a000 - 0x95c8afeb com.apple.SearchKit 1.3.0 (1.3.0) <9E18AEA5-F4B4-8BE5-EEA9-818FC4F46FD9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x95ce5000 - 0x95d3fff7 com.apple.framework.IOKit 2.0 (???) <7618DDEC-2E3B-9C6E-FDC9-15169E24B4FB> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x95d40000 - 0x95de8ff7 com.apple.QD 3.31 (???) <40FCAC85-4E4F-2290-90D4-F66D550ADFDC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x95de9000 - 0x95de9ff7 com.apple.vecLib 3.5 (vecLib 3.5) <17BEEF92-DF30-CD52-FD65-0B7B43B93617> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib 0x95e6a000 - 0x95e70fff com.apple.CommonPanels 1.2.4 (91) <2438AF5D-067B-B9FD-1248-2C9987F360BA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels 0x95f33000 - 0x95f47ffb com.apple.speech.synthesis.framework 3.10.35 (3.10.35) <57DD5458-4F24-DA7D-0927-C3321A65D743> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x95f48000 - 0x95f52fe7 com.apple.audio.SoundManager 3.9.3 (3.9.3) <5F494955-7290-2D91-DA94-44B590191771> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound 0x96277000 - 0x96281ff7 libGL.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib 0x96282000 - 0x96294ff7 com.apple.MultitouchSupport.framework 200.20 (200.20) <1D7EE15B-ADDD-1F57-F1FB-FB5252910D5A> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport 0x9638b000 - 0x963cfff3 com.apple.coreui 0.2 (112) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI 0x964ca000 - 0x96686fef com.apple.ImageIO.framework 3.0.0 (3.0.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x96687000 - 0x966d4feb com.apple.DirectoryService.PasswordServerFramework 6.0 (6.0) /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/PasswordServer 0x966d5000 - 0x966d5ff7 com.apple.Carbon 150 (152) <608A04AB-F35D-D2EB-6629-16B88FB32074> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 0x9677f000 - 0x9681bfe7 com.apple.ApplicationServices.ATS 4.0 (???) <81700C90-2614-F7E2-CC6A-B01C24A2BD75> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS 0x9681c000 - 0x96859ff7 com.apple.SystemConfiguration 1.10 (1.10) <897AEEAF-CF5D-2843-C33B-31A0A7C98A6A> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x9685a000 - 0x968dcffb SecurityFoundation ??? (???) <29C27E0E-B2B3-BF6B-B1F8-5783B8B01535> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation 0x968dd000 - 0x96b3fff3 com.apple.security 6.0 (36910) /System/Library/Frameworks/Security.framework/Versions/A/Security 0x96b40000 - 0x96b4efe7 libz.1.dylib ??? (???) <7B7A02AB-DA99-6180-880E-D28E4F9AA8EB> /usr/lib/libz.1.dylib 0x96c52000 - 0x97433497 com.apple.CoreGraphics 1.535.5 (???) <0B93D29C-D957-AD00-10F3-94112D75D6D9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x97434000 - 0x97434ff7 com.apple.Accelerate 1.5 (Accelerate 1.5) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x9754c000 - 0x97556ffb com.apple.speech.recognition.framework 3.10.10 (3.10.10) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition 0x97557000 - 0x9757bff7 libJPEG.dylib ??? (???) <265DBF67-994E-E320-4CB1-9C3DE792C3B2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x97763000 - 0x977dcff3 com.apple.audio.CoreAudio 3.2.0 (3.2) <91AE891E-6015-AABE-3512-2D5EBCA0937B> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio 0x977ee000 - 0x977f1ffb com.apple.help 1.3.1 (41) <67F1F424-3983-7A2A-EC21-867BE838E90B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help 0x97b07000 - 0x97b57ff7 com.apple.framework.familycontrols 2.0 (2.0) <50617342-E578-4C1C-938A-19A37ECA91CA> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls 0x97b58000 - 0x97b58ff7 com.apple.ApplicationServices 38 (38) <8012B504-3D83-BFBB-DA65-065E061CFE03> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x97b72000 - 0x97c68ff7 libGLProgrammability.dylib ??? (???) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib 0x97c69000 - 0x97d1bffb libFontParser.dylib ??? (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x97d27000 - 0x97d58ff7 libGLImage.dylib ??? (???) <0FB347C7-A579-4E51-4733-39AB28064554> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib 0x97d59000 - 0x97d6efff com.apple.ImageCapture 6.0 (6.0) <3F31833A-38A9-444E-02B7-17619CA6F2A0> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture 0x97d7a000 - 0x97e29ff3 com.apple.ink.framework 1.3 (104) <8526D880-D367-3EF9-DBFD-9A6AB240F57A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink 0x97ea5000 - 0x97f36fe3 com.apple.print.framework.PrintCore 6.0 (312) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x981e4000 - 0x981f8fe7 libbsm.0.dylib ??? (???) <14CB053A-7C47-96DA-E415-0906BA1B78C9> /usr/lib/libbsm.0.dylib 0x983f3000 - 0x98412fe7 com.apple.opencl 11 (11) <372A42E7-FB10-B74D-E1A0-980E94D07021> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL 0x98413000 - 0x98439fff com.apple.DictionaryServices 1.1 (1.1) <07694B30-56A9-5C98-B8BC-DA0628715FA8> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x9843a000 - 0x98447ff7 com.apple.opengl 1.6.3 (1.6.3) <59D86286-B46F-B0E4-68F8-E5CDCADE393E> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 0x988f7000 - 0x98c5bff7 com.apple.QuartzCore 1.6.0 (226.0) <7E29DD09-BE04-AA06-5C81-5C093F16901B> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore 0x98c5f000 - 0x98f82fef com.apple.HIToolbox 1.6.0 (???) <6F95AF67-678A-D8BC-FFC2-029C9AA2F44A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox 0x99181000 - 0x9922efe7 libobjc.A.dylib ??? (???) <410DD065-A18F-F054-0457-65525F4D1039> /usr/lib/libobjc.A.dylib 0x992f9000 - 0x99315fe3 com.apple.openscripting 1.3 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x9932c000 - 0x9932ffe7 libmathCommon.A.dylib ??? (???) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib 0x99330000 - 0x99358ff7 libxslt.1.dylib ??? (???) <769EF4B2-C1AD-73D5-AAAD-1564DAEA77AF> /usr/lib/libxslt.1.dylib 0x993d4000 - 0x993d8ff7 IOSurface ??? (???) /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface 0x993d9000 - 0x993fbff3 com.apple.DirectoryService.Framework 3.6 (621) <61569C79-6567-BE8F-4F76-BAC04E5FBF79> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService 0x993fc000 - 0x99408ff7 libkxld.dylib ??? (???) <152C8DBB-0149-5827-3240-E57CA85CFE5F> /usr/lib/system/libkxld.dylib 0xffff0000 - 0xffff1fff libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib Model: MacBookPro5,4, BootROM MBP53.00AC.B03, 2 processors, Intel Core 2 Duo, 2.53 GHz, 4 GB, SMC 1.49f2 Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB Memory Module: global_name AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.91.19) Bluetooth: Version 2.2.1f7, 2 service, 1 devices, 1 incoming serial ports Network Service: AirPort, AirPort, en1 Serial ATA Device: Hitachi HTS545025B9SA02, 232,89 GB Serial ATA Device: MATSHITADVD-R UJ-868 USB Device: iPod, 0x05ac (Apple Inc.), 0x1261, 0x24100000 USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0x24400000 USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0x26500000 USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x04500000 USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0237, 0x04600000 USB Device: USB Receiver, 0x046d (Logitech Inc.), 0xc526, 0x06200000 USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000 USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8213, 0x06110000 ---------- messages: 1483 nosy: MNilson priority: critical status: unread title: Error when running a code _______________________________________________________ PSF Meta Tracker _______________________________________________________