[x264-devel] core dump on solaris 10/space withx264-snapshot-20100112-2245

[Sean McGovern]

BTW how do you get your core files to have useful names?

-- Sean
-----Original Message-----
From: Chris Brookes <cbrookes at gmail.com>
Date: Fri, 15 Jan 2010 15:40:41 
To: Mailing list for x264 developers<x264-devel at videolan.org>
Subject: Re: [x264-devel] core dump on solaris 10/space with
	x264-snapshot-20100112-2245

2010/1/14 Jason Garrett-Glaser <darkshikari at gmail.com>:

>>> I'm going to guess int dmf = dequant_mf[i_qp%6][0], but that makes no
>>> sense whatsoever.
>>
>> Current function is x264_mb_encode_8x8_chroma
>>   55           int d0 = dct[0] + dct[1]; \
>
> That's impossible.  There's no way it can crash on that line without
> an utterly horrific compiler failure.
>
> At this point, I would be inclined to blame GCC.

OK, an eagle eyed mailing list reader pointed out that the \
characters I left in the code I pasted would mean the pre-processor
would merge the lines and make the crash point as unfathomable as
having the macro. I took those out and back with gcc 3.4.6 sure enough
it cores at the point you guessed.

Current function is x264_mb_encode_8x8_chroma
   59       int dmf = dequant_mf[i_qp%6][0];
(dbx) where
current thread: t at 1
=>[1] x264_mb_encode_8x8_chroma(h = 0xab340, b_inter = 0, i_qp = 19),
line 59 in "macroblock.c"
  [2] x264_macroblock_encode(h = 0xab340), line 892 in "macroblock.c"
  [3] x264_rd_cost_mb(h = 0xab340, i_lambda2 = 2925), line 145 in "rdo.c"
  [4] x264_macroblock_analyse(h = 0xab340), line 992 in "analyse.c"
  [5] x264_slice_write(h = 0xab340), line 1672 in "encoder.c"
  [6] x264_encoder_encode(h = 0xab340, pp_nal = 0xffbff18c, pi_nal =
0xffbff188, pic_in = 0x3f, pic_out = 0xffbff1e0), line 1904 in
"encoder.c"
  [7] main(argc = 0, argv = 0xa9a10), line 1236 in "x264.c"
_______________________________________________
x264-devel mailing list
x264-devel at videolan.org
http://mailman.videolan.org/listinfo/x264-devel