Beagle crash on startup

dump attached

This looks to be a mono bug.

Same here. Edgy Eft.

same here i attached my crash report

The same on Edgy Eft AMD64.

same here feisty amd64

Yeah I've got the same problem with an AMD64 X2 4200 running Edgy (32bit). Crashed on startup.

Same here

same problem. ubuntu edgy. intel.

Hi,
  The crash dump is not entirely useful for beagle. It will be helpful if anyone who saw the problem could attach the ~/.beagle/Log directory (tar-gzipped) to the bug.
Thanks.

Here you go, I only started having the problem recently, (last few days) so I've only included the logs for about a week.

Thanks Kevin. Unfortunately the log files dont point to anything wrong in beagle. Its extremely important to figure out the right stacktrace - unfortunately the apport crashdump is not very helpful for mono programs. Can you change your beagled startup code as
"beagled 2>~/.beagle/crash"

(instead of just beagled). I am hoping to get something inside ~/.beagle/crash file when beagle crashes.

If you dont know how to do that, let me know. I will post the steps. Thanks.

To figure out what is crashing beagle we need the mono stracktrace. Please see this http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login

Same here, edgy intel 32bit

Same thing

Same thing, attach beagle log.

Attached is a crash "stacktrace" (report) generated using the second method described on http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login . It ends with an address boundary error.

Beagled crashes not only when I log in, but consistently every time I start it. I just start it from the command line and watch it crash after about 1 minute. Let me know if this is not a duplicate bug and I should submit a separate report. My command shell is Fish (the Friendly Interactive Shell). I am running Ubuntu Edgy Eft on an Intel 32-bit processor.

Here is a second report, which also ends with an address boundary error, but is slightly different, and so I include it for our common amusement.

I should say that the other suggested methods of creating a stacktrace -- "beagled 2> ~/.beagle/crash" and using "exec -a $PROCESS_NAME $CMDLINE 2>~/.beagle/crash &" /usr/bin/beagled create an empty file. There is no output.

What is "fish"?

Normally when a mono app crashes it prints out a bunch of stuff to the console about its stack trace at the time, but it doesn't seem to happen for you because (I am guessing) that fish is trapping it.

Oh, I see that you describe what fish is above. :) Can you try running it under bash or another shell instead?

Of course, you are right that the reported address boundary error is Fish-specific.

It's interesting that this bug does not occur on my other Ubuntu 6.10 box, which should have the same versions of Beagle and other Mono apps and libraries. But the content that is indexed is different.

> ** Attachment added: ""beagled --fg" from sh"
> http://librarian.launchpad.net/7124666/beagled_crash_4.txt

Beagle must be messing (exposing ?) up something deep inside mono.
Even mono sigsegv handler is not getting invoked!

Yeah, very bizarre!

The next thing to try would be to attach gdb to the process and get a threaded stack trace when it crashes.

Philip,
  could you do the following ? (it will be very helpful).
1) Put this in your .gdbinit in your home directory
------->8-------------
define mono_backtrace
 select-frame 0
 set $i = 0
 while ($i < $arg0)
   set $foo = mono_pmip ($pc)
   if ($foo == 0x00)
     frame
   else
     printf "#%d %p in %s\n", $i, $pc, $foo
   end
   up-silently
   set $i = $i + 1
 end
end
------------------>8--------------
2) start beagled from the terminal as
beagled --fg --indexing-delay 300
then from another terminal,
3) find out the pid of beagle, $ ps ux | grep beagled
4) start gdb $ gdb --pid=<pid of beagled>
5) once gdb starts, enter at the gdb prompt
handle SIGXCPU SIG33 SIG35 SIGPWR nostop noprint
6) Enter at the gdb prompt
c or continue
7) when beagled crashes, enter this at gdb prompt
mono_backtrace 10
8) Copy the output of mono_backtrace to a file and attach it.
9) At gdb prompt, type q or quit
10) If it asks to detach, say yes.
11) Kill beagled if it is still running

Its a long process but not tedious :-). You can almost reliably reproduce the crash, so I am seeking your help. Thanks.

Beagle crashed for no apparent reason - well nothing I did anyway. I was just composing a note with the gapplet Sticky Notes 2.16.1.
Dump attached. On startup,

Cascade: if you're running the released version of Feisty, can you attach your ~/.beagle/Log/current-Beagle file to the bug? It should have the printed output from Mono when it crashed.

Beagled does not crash if I attach it to the gdb process. It crashes reliably if I start it without. The gdb output is attached.

Beagled stops crashing if I remove /etc from the list of directories to index, in addition to my home directory. If any subdirectory of /etc is listed , beagled crashes as above. Other root subdirectories, such as /usr have no effect either way.

Philip: Interesting. Can you check the logs (in ~/.beagle/Log) to see what files it might be crashing on?

The crash only occurs with the "files" backend:

    beagled --backend files --fg --debug

I set only the directory /etc/sound/events to be indexed. No IndexHelper log file is created, and the current-Beagle log file (~/.beagle/Log/current-Beagle) mentions "/etc" only on the second-last line:

    070502 1733022546 06253 Beagle DEBUG: Adding root: /etc/sound/events

Followed by:

    070502 1733024881 06253 Beagle DEBUG: Loaded 4874 records from /home/philip/.beagle/Indexes/FileSystemIndex/FileAttributesStore.db in 0.145s

If I move the .db file mentioned above, beagled does not crash. So I guess the problem is that this file is corrupt, and beagled does not cope with this.

Philip: interesting. It would be helpful if you could email me the logs and the DB file, if possible. (<email address hidden>)

Joe, I sent you my .beagle/Indexes/FileSystemIndex/FileAttributesStore.db . Unfortunately the log file has been erased because I waited so long to reply, and beagle apparently creates a new file every time my laptop comes back from sleep.

The good news is that the crash seems to be gone after I upgraded my Ubuntu box to Feisty Fawn yesterday. The bad news is that we will probably not know what the problem was. I installed the old version again and tried with the index file, but there is no crash anymore.

If I run the new beagle with the old index, I get warning messages about a version mismatch:

Always: Starting Beagle Daemon (version 0.2.16.3)
Always: Running on Mono 1.2.3.1
Always: Using sqlite version 3
Always: Command Line: /usr/lib/beagle/BeagleDaemon.exe --fg --indexing-delay 3
Warn: Unable to create read-only index (likely due to index version
mismatch): /var/cache/beagle/indexes/applications
Warn: Unable to create read-only index (likely due to index version
mismatch): /var/cache/beagle/indexes/documentation
Always: Starting Index Helper process (version 0.2.16.3)
Always: Running on Mono 1.2.3.1
Always: Using sqlite version 3
Always: Extended attributes are supported
Always: Command Line: /usr/lib/beagle/IndexHelper.exe

If I see any more issues I will report.

Received the error on reboot, had been trying to set up samba connections to a windows file server.

Gary: Use a newer version. 0.2.16.3 is in feisty, or you can get updated edgy packages here: http://beagle-project.org/files/ubuntu/edgy/

> ** Changed in: beagle (Ubuntu)
> Status: Incomplete => Fix Released

The status was changed to "Fix Released". I am interested to know what was the
fix. Link to the relevant patch or some relevant discussion or any other
pointers ?