[Mono-bugs] [Bug 672446] [regression] native stacktrace when Castle generic Resolve by anonymous object

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=672446

https://bugzilla.novell.com/show_bug.cgi?id=672446#c4


Maciej Paszta <maciej.paszta at mlabs.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #4 from Maciej Paszta <maciej.paszta at mlabs.pl> 2011-02-21 09:42:27 UTC ---
I've tested it under Mono 2.10 downloaded from offical Mono Repository for SLES
SP1 - the test still fails. Version string is:
Mono JIT compiler version 2.10 (tarball Mon Feb 14 20:00:49 UTC 2011)
Installed packages:
mono-data-oracle-2.10-12.1
mono-wcf-2.10-12.1
mono-addon-winforms-2.6.7-0.1.1
mono-debugger-2.10-32.4
mono-winforms-2.10-12.1
mono-addon-data-postgresql-2.6.7-0.1.1
mono-addon-xsp-2.6.5-0.1.3
mono-core-2.10-12.1
mono-getoptions-2.6-1.4
monodoc-core-2.10-12.1
mono-mvc-2.10-12.1
mono-addon-check-0.2-2.2
mono-addon-core-2.6.7-0.1.1
mono-addon-data-sqlite-2.6.7-0.1.1
mono-addon-libgdiplus0-2.6.7-0.6.1
mono-core-debuginfo-2.10-12.1
libmono-llvm0-2.10-12.1
mono-web-2.10-12.1
mono-tools-2.10-35.2
mono-devel-2.10-12.1
mono-addon-web-2.6.7-0.1.1
mono-data-2.10-12.1
mono-nunit-2.10-12.1
mono-addon-data-2.6.7-0.1.1
libmono-2_0-1-2.10-12.1
mono-data-sqlite-2.10-12.1
mono-extras-2.10-12.1


However, I have another machine which is a VM downloaded from you website.
Originally it had Mono 2.8.1, but I have upgraded it to:
mono-check-0.2-1.2.noarch
mono-debugger-2.10-32.4.i586
mono-data-postgresql-2.10-12.1.i586
mono-web-2.10-12.1.i586
mono-nunit-2.10-12.1.i586
monodevelop-2.4.2-1.11.noarch
monodevelop-debugger-gdb-2.4-3.5.noarch
libmono-llvm0-2.10-12.1.i586
apache2-mod_mono-2.10-20.3.i586
mono-wcf-2.10-12.1.i586
mono-uia-2.1-8.3.i586
mono-tools-2.10-35.2.noarch
monodoc-http-2.10-35.2.noarch
libmono-2_0-1-2.10-12.1.i586
mono-locale-extras-2.10-12.1.i586
libmonosgen-2_0-devel-2.10-12.1.i586
mono-extras-2.10-12.1.i586
mono-winfxcore-2.10-12.1.i586
monotools-server-gui-2.0.7180-2.19.noarch
mono-uia-devel-2.1-8.3.i586
monodevelop-python-2.4-1.59.noarch
monodevelop-boo-2.4-1.60.noarch
monodoc-core-2.10-12.1.i586
mono-zeroconf-0.9.0-5.1.noarch
mono-data-2.10-12.1.i586
mono-data-oracle-2.10-12.1.i586
mono-mvc-2.10-12.1.i586
mono-addins-0.5-32.11.noarch
monodevelop-vala-2.4-1.21.noarch
monodevelop-database-2.4-2.56.noarch
mono-zeroconf-provider-avahi-0.9.0-5.1.noarch
libmonosgen-2_0-0-2.10-12.1.i586
libmono-2_0-devel-2.10-12.1.i586
monotools-server-2.0.7180-2.19.noarch
mono-devel-2.10-12.1.i586
mono-complete-2.10-12.1.i586
mono-zeroconf-doc-0.9.0-5.1.noarch
mono-zeroconf-devel-0.9.0-5.1.noarch
mono-core-2.10-12.1.i586
mono-getoptions-2.6-1.11.noarch
mono-data-sqlite-2.10-12.1.i586
mono-winforms-2.10-12.1.i586
mono-basic-2.10-31.9.noarch
monodevelop-debugger-mdb-2.4-1.55.noarch

The version is is the same as on the SLES 11 machine:
Mono JIT compiler version 2.10 (tarball Mon Feb 14 20:21:29 UTC 2011)

On this machine test case is successful. Maybe the architecture has something
to do with it? SLES11 is on x64 but VM machine is x86?

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.