gshare-manager.exe crashed with SIGSEGV in g_datalist_clear()

[StoatWblr]

Binary package hint: gshare

auto-generated report

ProblemType: Crash
Architecture: i386
Date: Thu Jun 28 11:44:12 2007
Disassembly: 0xb679bf38:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/gshare/gshare-manager.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: cdrom
Package: gshare 0.94-3
PackageArchitecture: all
ProcCmdline: /usr/bin/mono /usr/lib/gshare/gshare-manager.exe
ProcCwd: /home/alan
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gshare
Stacktrace:
 #0 0xb679bf38 in ?? ()
 #1 0xb7f09408 in g_datalist_clear () from /usr/lib/libglib-2.0.so.0
 #2 0xb699bd58 in ?? () from /usr/lib/libgobject-2.0.so.0
 #3 0x083596f8 in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 g_datalist_clear () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()
Title: gshare-manager.exe crashed with SIGSEGV in g_datalist_clear()
Uname: Linux msslqd 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Vincent Legout (vlegout)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems. [WWW] http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[Vincent Legout (vlegout)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!