03:35 <znz_v> biff: [ruby-changes:26907] akr:r38959 (trunk): * ext/fcntl/fcntl.c: update document. use "file descriptor" instead - http://mla.n-z.jp/?ruby-changes=26907

03:35 <znz_v> biff: [ruby-changes:26908] svn:r38960 (trunk): * 2013-01-28 - http://mla.n-z.jp/?ruby-changes=26908

08:51 <znz_v> biff: [ruby-changes:26909] nobu:r38961 (trunk): envutil.rb: no core dump - http://mla.n-z.jp/?ruby-changes=26909

09:02 <znz_v> biff: [ruby-changes:26910] nobu:r38962 (trunk): vm_backtrace.c: use long - http://mla.n-z.jp/?ruby-changes=26910

15:50 <zmoazeni> Hi there, I'm investigating seemingly random segfaults from 1.9.3p125, p327, and p374 (I don't think it's a ruby bug). But I'm new to reading these reports. Can someone help me or point me to some documentation that describes which each of these variables are? "c" "p" "s" "b'… "c:0118 p:---- s:0664 b:0664 l:000663 d:000663 CFUNC :load" (right after "-- Control frame information --")

15:51 <zmoazeni> I assume it describes information about the stack frame?

15:52 <zzak> correct

15:55 <zzak> zmoazeni: thats a good question

15:55 <zmoazeni> Does "b" stand for "block"? blocks of the stack frame that are allocated at a time?

15:55 <zzak> all i can think of is they might be the type of events

15:55 <zzak> yes

15:55 <zzak> "c" would be a ruby or C call

15:55 <zmoazeni> Any idea how large those block sizes are? Or is that architecture dependent?

15:55 <zzak> "b" would be a block call or return

15:56 <zzak> idk what "p" or "s" would be

15:56 <zzak> im just guessing based off tracepoint / set_trace_func

15:56 <zmoazeni> I thought maybe "p" stood for "page"?

15:56 <zmoazeni> like a page i memory

15:56 <zmoazeni> *in memory

15:57 <zzak> or "d"

15:57 <zzak> _ko1: maybe koichi-san can help us :)

16:08 <zzak> zmoazeni: https://twitter.com/_ko1/status/295924563261419520

16:09 <zmoazeni> zzak: Ahh thanks!

16:10 <zzak> :)