FS#46608 - [mono] 4.0.4.1-1 mkbundle produces faulty binaries
Attached to Project:
Arch Linux
Opened by Thomas Weidner (thomas001le) - Thursday, 08 October 2015, 11:42 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 27 March 2016, 18:27 GMT
Opened by Thomas Weidner (thomas001le) - Thursday, 08 October 2015, 11:42 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 27 March 2016, 18:27 GMT
|
Details
mkbundle should produce stand-alone binaries from mono
assemblies. In Archlinux (64bit), even a simple hello world
program produces a binary which segfaults:
$ cat Hello.cs public class Hello1 { public static void Main() { System.Console.WriteLine("Hello, World!"); } } $ dmcs Hello.cs $ mkbundle Hello.exe OS is: Linux Sources: 1 Auto-dependencies: False embedding: /home/thomas/tmp/Hello.exe Compiling: as -o temp.o temp.s cc -ggdb -o a.out -Wall temp.c `pkg-config --cflags --libs mono-2` temp.o Done $ ./a.out Native stacktrace: /usr/lib/libmonoboehm-2.0.so.1(+0xd33ca) [0x7f064c8a43ca] /usr/lib/libmonoboehm-2.0.so.1(+0x488e0) [0x7f064c8198e0] /usr/lib/libpthread.so.0(+0x10d60) [0x7f064bebad60] /usr/lib/libmonoboehm-2.0.so.1(+0x243a40) [0x7f064ca14a40] /usr/lib/libmonoboehm-2.0.so.1(+0x24bef8) [0x7f064ca1cef8] /usr/lib/libmonoboehm-2.0.so.1(+0x244f3f) [0x7f064ca15f3f] /usr/lib/libmonoboehm-2.0.so.1(+0x244308) [0x7f064ca15308] /usr/lib/libmonoboehm-2.0.so.1(+0x23af68) [0x7f064ca0bf68] /usr/lib/libmonoboehm-2.0.so.1(+0x23b851) [0x7f064ca0c851] /usr/lib/libmonoboehm-2.0.so.1(+0x245e6a) [0x7f064ca16e6a] /usr/lib/libmonoboehm-2.0.so.1(+0x245f8e) [0x7f064ca16f8e] /usr/lib/libmonoboehm-2.0.so.1(+0x1fc0a1) [0x7f064c9cd0a1] /usr/lib/libmonoboehm-2.0.so.1(+0x1d079c) [0x7f064c9a179c] /usr/lib/libmonoboehm-2.0.so.1(+0x49be6) [0x7f064c81abe6] /usr/lib/libmonoboehm-2.0.so.1(mono_main+0x2d9) [0x7f064c8799c9] ./a.out() [0x400bfb] /usr/lib/libc.so.6(__libc_start_main+0xf0) [0x7f064bb26610] ./a.out() [0x4007c9] Debug info from gdb: ptrace: Operation not permitted. No threads. ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= Aborted (core dumped) |
This task depends upon
Closed by Isenmann Daniel (ise)
Sunday, 27 March 2016, 18:27 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in newest version, thanks for the help.
Sunday, 27 March 2016, 18:27 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in newest version, thanks for the help.
ChangeLog:
- './configure' cleanup
- '!makeflags' removed (mono build finished successfully on x86_64)
- md5sums -> sha256sums
- pkgbuild cleanup
- update pkgver=4.3.2.467
TEST:
$ dmcs Hello.cs
$ mkbundle Hello.exe
OS is: Linux
Sources: 1 Auto-dependencies: False
embedding: /home/darek/tmp/Hello.exe
AS = as (default)
[execute cmd]: as -o temp.o temp.s
Compiling:
CC = cc (default)
[execute cmd]: cc -ggdb -o a.out -Wall temp.c `pkg-config --cflags --libs mono-2` temp.o
Done
$ ./a.out
Hello, World!
$ mono Hello.exe
Hello, World!
mono.install (0.1 KiB)
mono.binfmt.d (0 KiB)