[Mono-bugs] [Bug 77950][Blo] New - "Can't find current process" when running beagled

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Mar 29 13:46:07 EST 2006

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by kellermg at potsdam.edu.


--- shadow/77950	2006-03-29 13:46:07.000000000 -0500
+++ shadow/77950.tmp.6651	2006-03-29 13:46:07.000000000 -0500
@@ -0,0 +1,62 @@
+Bug#: 77950
+Product: Mono: Runtime
+Version: 1.1
+OS Details: Fedora Core 5
+Status: NEW   
+Priority: Blocker
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: kellermg at potsdam.edu               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: "Can't find current process" when running beagled
+Description of Problem:
+This is being entered at the request of Joe Shaw <joeshaw at novell.com> from
+the Beagle group.
+beagle 0.2.3-4 and mono running on Fedora Core 5. beagled starts
+up and runs for a minute or so, belches (with --debug):
+20050722T130000 is a recurrence instance
+20050722T130000 is a recurrence instance
+20050713T122210Z-5438-500-1-0 at wasp-73-246.potsdam.edu has recurrences
+** (/usr/lib/beagle/IndexHelper.exe:1051): WARNING **:
+process_set_current: error looking up process handle 0xffffffff
+Unhandled Exception: System.SystemException: Can't find current process
+in [0x0002b]
+System.Diagnostics.Process:GetCurrentProcess ()
+in [0x000bd]
+(at /usr/src/build/724867-i386/BUILD/beagle-0.2.3/Util/Log.cs:216)
+Beagle.Util.Log:WriteLine (LogLevel level, System.String format,
+System.Object[] args, System.Exception ex)
+in [0x00004]
+(at /usr/src/build/724867-i386/BUILD/beagle-0.2.3/Util/Log.cs:315)
+Beagle.Util.Log:Error (System.String message, System.Object[] args)
+in [0x00002]
+(at /usr/src/build/724867-i386/BUILD/beagle-0.2.3/Util/Logger.cs:95)
+Beagle.Util.Logger:Error (System.String message, System.Object[] args)
+in [0x0001c]
+Beagle.IndexHelper.IndexHelperTool:Main (System.String[] args)
+The bottom block (debug output) is repeated periodically (60 seconds) ad
+Under FC4, I had mono and beagle working, indexing the same
+homedirectory with no problems. I wiped out ~/.beagle  after the problem
+first cropped up, thinking it may have been an <insert plausible
+explanation here> related to old/corrupted data. It didn't help,
+unfortunately. At Joe's request I also moved out ~/.wapi, but that didn't
+change anything either. The beagle logs are all 0 byte, as well. Thoughts?
+Ideas for further testing? Would an strace help?

More information about the mono-bugs mailing list