[Mono-bugs] [Bug 60296][Wis] New - monodis segfaults when one dependency cannot be resolved

[bugzilla-daemon@bugzilla.ximian.com]

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 blade@debian.org.

http://bugzilla.ximian.com/show_bug.cgi?id=60296

--- shadow/60296	2004-06-16 12:50:46.000000000 -0400
+++ shadow/60296.tmp.8320	2004-06-16 12:50:46.000000000 -0400
@@ -0,0 +1,57 @@
+Bug#: 60296
+Product: Mono: Runtime
+Version: unspecified
+OS: GNU/Linux [Other]
+OS Details: Debian Sid (packaging beta3)
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: blade@debian.org               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: monodis segfaults when one dependency cannot be resolved
+
+Description of Problem:
+
+The topic says it all - if a refered assembly does not exist and you run
+monodis --assemblyref foobar.dll, the program simply segfaults:
+
+monodis --assemblyref
+debian/tmp/usr/lib/mono/gac/gnomedb-sharp/1.0.0.0__35e10195dab3c99f/gnomedb-sharp.dll
+
+** (process:14897): WARNING **: Could not find assembly glib-sharp,
+references from
+/dbuild/wdir/gtk-sharp-0.98/debian/dev/build-area/gtk-sharp-0.98/debian/tmp/usr/lib/mono/gac/gnomedb-sharp/1.0.0.0__35e10195dab3c99f/gnomedb-sharp.dll
+(assemblyref_index=1)
+     Major/Minor: 1,0
+     Build:       0,0
+     Token:       35e10195dab3c99f
+
+Speicherzugriffsfehler
+
+Actual Results:
+
+The segfault. No matter which component is missing, the first thing it does
+is the segfault.
+
+
+Expected Results:
+
+I expect it to print some valid data on STDIN in the format:
+
+Version=2.0.3600.0
+        Name=System.Xml
+        Public Key:
+0x00000000: B7 7A 5C 56 19 34 E0 89 
+
+We on this data to create a sane dependency chain between the Debian
+packages (to use it with APT).
+
+Side note: One thing I wonder about: I have set my LANG to C, but I see
+Speicherzugriffsfehler instead of "Segmentation fault" so something may
+invoke a new shell or whatever... or glib goes strange ways, again.