[Mono-bugs] [Bug 462016] make check for pinvoke2.exe fails for PowerPC

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri Jan 2 12:06:56 EST 2009


User munroesj at us.ibm.com added comment

--- Comment #12 from Steven Munroe <munroesj at us.ibm.com>  2009-01-02 10:06:56 MST ---
At Mark Probst request tried to run that same none patched revision of mono

This fails in the sam way:

mono/tests> gdb ../mini/mono
GNU gdb
Copyright (C) 2007 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "ppc-suse-linux"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) handle SIGXCPU SIG33 SIG35 SIGPWR nostop noprint
Signal        Stop      Print   Pass to program Description
SIGXCPU       No        No      Yes             CPU time limit exceeded
SIGPWR        No        No      Yes             Power fail/restart
SIG33         No        No      Yes             Real-time event 33
SIG35         No        No      Yes             Real-time event 35
(gdb) set environment MONO_PATH ../../../mcs/class/lib/net_2_0
(gdb) set environment MONO_SHARED_DIR
(gdb) set environment MONO_CFG_DIR
(gdb) set environment MONO_GENERIC_SHARING none
(gdb) run pinvoke2.exe
Starting program: /home/sjmunroe/src/mono-ppc/mono-svn/mono/mono/mini/mono
[Thread debugging using libthread_db enabled]
[New Thread 0xf7fb6210 (LWP 4229)]
[New Thread 0xf77a34a0 (LWP 4232)]
[New Thread 0xf77434a0 (LWP 4233)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf7fb6210 (LWP 4229)]
0x100aeabc in mono_class_native_size (klass=0x102f55f0, align=0xff8d91c8)
    at marshal.c:11596
11596           return klass->marshal_info->native_size;

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

More information about the mono-bugs mailing list