Hi
Allow loading the per-directory .gdbinit from your ~/.gdbinit.
If you have no problems with the security allow from the root:
set auto-load safe-path /
regards
m
On 20151208 12:19 , CrisKolkman wrote:
Now I'm getting a 503 error and the /var/log/httpd/error_log shows:
Native stacktrace:
/usr/bin/mono() [0x4a29f2]
/lib64/libpthread.so.0(+0xf130) [0x7f9f9cb36130]
/lib64/libc.so.6(gsignal+0x37) [0x7f9f9c5855d7]
/lib64/libc.so.6(abort+0x148) [0x7f9f9c586cc8]
/usr/bin/mono() [0x633fd9]
/usr/bin/mono() [0x63424c]
/usr/bin/mono() [0x6343e3]
/usr/bin/mono() [0x5a7f9b]
/usr/bin/mono() [0x423d9e]
/usr/bin/mono(mono_main+0x38f) [0x47625f]
/lib64/libc.so.6(__libc_start_main+0xf5) [0x7f9f9c571af5]
/usr/bin/mono() [0x41ee35]
Debug info from gdb:
warning: File "/usr/bin/mono-sgen-gdb.py" auto-loading has been declined by
your `auto-load safe-path' set to
"$debugdir:$datadir/auto-load:/usr/bin/mono-gdb.py".
To enable execution of this file add
add-auto-load-safe-path /usr/bin/mono-sgen-gdb.py
line to your configuration file "$HOME/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "$HOME/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the
shell:
info "(gdb)Auto-loading safe path"
[New LWP 12602]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007f9f9cb35cd9 in waitpid () from /lib64/libpthread.so.0
Id Target Id Frame
2 Thread 0x7f9f9bbff700 (LWP 12602) "mono" 0x00007f9f9cb32705 in
pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
* 1 Thread 0x7f9f9d662780 (LWP 12601) "mono" 0x00007f9f9cb35cd9 in
waitpid () from /lib64/libpthread.so.0
Thread 2 (Thread 0x7f9f9bbff700 (LWP 12602)):
#0 0x00007f9f9cb32705 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1 0x00000000006025cc in thread_func ()
#2 0x00007f9f9cb2edf5 in start_thread () from /lib64/libpthread.so.0
#3 0x00007f9f9c6461ad in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7f9f9d662780 (LWP 12601)):
#0 0x00007f9f9cb35cd9 in waitpid () from /lib64/libpthread.so.0
#1 0x00000000004a2ab6 in mono_handle_native_sigsegv ()
#2 <signal handler called>
#3 0x00007f9f9c5855d7 in raise () from /lib64/libc.so.6
#4 0x00007f9f9c586cc8 in abort () from /lib64/libc.so.6
#5 0x0000000000633fd9 in monoeg_log_default_handler ()
#6 0x000000000063424c in monoeg_g_logv ()
#7 0x00000000006343e3 in monoeg_assertion_message ()
#8 0x00000000005a7f9b in mono_init_internal ()
#9 0x0000000000423d9e in mini_init ()
#10 0x000000000047625f in mono_main ()
#11 0x00007f9f9c571af5 in __libc_start_main () from /lib64/libc.so.6
#12 0x000000000041ee35 in _start ()
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
[Tue Dec 08 12:32:00.174916 2015] [:error] [pid 3915] Failed to connect to
mod-mono-server after several attempts to spawn the process.
--
View this message in context:
http://mono.1490590.n4.nabble.com/Mono-not-working-tp4667109p4667113.html
Sent from the Mono - ASP.NET mailing list archive at Nabble.com.
_______________________________________________
Mono-aspnet-list mailing list
Mono-aspnet-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-aspnet-list
_______________________________________________
Mono-aspnet-list mailing list
Mono-aspnet-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-aspnet-list
