[erlang-bugs] Segmentation fault in erts_printf_char (R13B04)

Kustarto Widoyo <>
Tue Mar 8 09:13:56 CET 2011


 > Could you supply the rest of the stack, i.e. who calls the print_term
 > function?

The following is about the rest of the stack (result of thread apply 
all bt).
...
Thread 1 (process 14798):
#0  0x0000000000585ea8 in erts_printf_char (fn=0x5880f0 <write_ds>,
     arg=0xb750930, c=91 '[') at common/erl_printf_format.c:840
#1  0x000000000048c6d8 in print_term (fn=0x5880f0 <write_ds>, arg=0xb750930,
     obj=5800176, dcount=0x458f2bc8) at beam/erl_printf_term.c:346
#2  0x000000000048c740 in print_term (fn=0x5880f0 <write_ds>, arg=0xb750930,
     obj=<value optimized out>, dcount=0x458f2bc8) at 
beam/erl_printf_term.c:349
#3  0x000000000048c740 in print_term (fn=0x5880f0 <write_ds>, arg=0xb750930,
     obj=<value optimized out>, dcount=0x458f2bc8) at 
beam/erl_printf_term.c:349
#4  0x000000000048c740 in print_term (fn=0x5880f0 <write_ds>, arg=0xb750930,
     obj=<value optimized out>, dcount=0x458f2bc8) at 
beam/erl_printf_term.c:349

....snip....

#43669 0x000000000048c740 in print_term (fn=0x5880f0 <write_ds>,
     arg=0xb750930, obj=<value optimized out>, dcount=0x458f2bc8)
     at beam/erl_printf_term.c:349
#43670 0x000000000048cf48 in erts_printf_term (fn=0xb750930, arg=0x44ef4004,
     term=1, precision=56331) at beam/erl_printf_term.c:452
#43671 0x0000000000586b9c in erts_printf_format (fn=0x5880f0 <write_ds>,
     arg=0xb750930, fmt=<value optimized out>, ap=0x458f2cd0)
     at common/erl_printf_format.c:813
#43672 0x0000000000587df4 in erts_vdsprintf (dsbufp=0xb750930,
     format=0x591897 "   %T\n", arglist=0x458f2cd0) at 
common/erl_printf.c:419
#43673 0x0000000000470fe0 in erts_print (to=<value optimized out>, arg=0x1,
     format=0x1c2510 <Address 0x1c2510 out of bounds>) at beam/utils.c:299
#43674 0x00000000004921a3 in erts_program_counter_info (to=-4,
     to_arg=0xb750930, p=0x2aaabb0ae630) at beam/erl_process.c:8387
#43675 0x00000000004921f5 in erts_stack_dump (to=-4, to_arg=0xb750930, 
p=0x1)
     at beam/erl_process.c:8360
#43676 0x00000000004e9191 in print_process_info (to=-4, to_arg=0xb750930,
     p=0x2aaabb0ae630) at beam/break.c:343
#43677 0x00000000004e9384 in process_info (to=-4, to_arg=0xb750930)
     at beam/break.c:79
#43678 0x0000000000458744 in system_info_1 (A__p=0x2aaabb0b6ca0, A_1=24459)
     at beam/erl_bif_info.c:1973
#43679 0x000000000051279a in process_main () at beam/beam_emu.c:2087
#43680 0x000000000049fac2 in sched_thread_func (vesdp=<value optimized out>)
     at beam/erl_process.c:3060
#43681 0x0000000000585314 in thr_wrapper (vtwd=<value optimized out>)
     at common/ethread.c:480
#43682 0x0000003383006367 in start_thread () from /lib64/libpthread.so.0
#43683 0x00000033824d309d in clone () from /lib64/libc.so.6

 > Also, by using the etp-commands gdb macros (in source tree,
 > $ERL_TOP/erts/etc/unix/), you could see the term that's being printed.
 > Is it corrupted?

Sorry, I am still not able to use it.

Thanks,
Widoyo



More information about the erlang-bugs mailing list