Description:
I have just installed a 'racket 5.3.6-2' package and not able to start any of binaries in it.
For example:

# racket
Welcome to Racket v5.3.6.
Segmentation fault (core dumped)

# drracket
Segmentation fault (core dumped)

# raco
Segmentation fault (core dumped)

Additional info:
racket 5.3.6-2
Linux dimsuzhost 3.12.1-3-ARCH #1 SMP PREEMPT Tue Nov 26 11:17:02 CET 2013 x86_64 GNU/Linux

Steps to reproduce:
Start any binary from above examples

I tried to see backtrace of the crash in gdb:

#0 0x00007ffff7b021c8 in scheme_gmp_tls_unload () from /usr/lib/libracket3m-5.3.6.so
#1 0x00007ffff7acb4b3 in done_with_GC () from /usr/lib/libracket3m-5.3.6.so
#2 0x00007ffff7b0bb11 in garbage_collect () from /usr/lib/libracket3m-5.3.6.so
#3 0x00007ffff7b11f7e in GC_malloc_one_tagged () from /usr/lib/libracket3m-5.3.6.so
#4 0x00007ffff7860284 in scheme_malloc_fail_ok () from /usr/lib/libracket3m-5.3.6.so
#5 0x00007ffff7aecf4c in scheme_make_vector () from /usr/lib/libracket3m-5.3.6.so
...

But the thing is that googling this told me that this is some common signal and it should be ignored during debugging, it most probably is not the issue.
It was advised to disable it in gdb session, but if I do this, nothing else pops up.