search for: 0000005b

...edx: 00000000 esi: b723f2b0 edi: f749ca78 ebp: 00000046 esp: f50b3e28 ds: 007b es: 007b ss: 0068 Process asterisk (pid: 5430, threadinfo=f50b2000 task=f7bbf060) Stack: 462f0587 00000000 41a0d314 00000000 000001ff 00000001 00000246 00000001 00000000 00000000 f50b3f38 00000000 0000005b 00000001 dfcf089c f50b3ebc f50b3efc f61ae400 f6a0d3b4 0000005b 0000005b f6a0d314 00000000 00000001 Call Trace: [<c013f4f8>] generic_file_aio_write+0x58/0xc0 [<f88f80db>] ext3_file_write+0x1b/0x93 [ext3] [<c0159466>] do_sync_write+0xb6/0x110 [<f8a7ac33>] zt_i...

Hi, I have an interesting problem that the dial out via sip always generates 603 error The following is the sip debug Your help is appreciated. CK == Using SIP RTP CoS mark 5 -- Executing [998560848 at DLPN_DP1:1] Dial("SIP/6100-0000005b", "SIP/13398560848 at hkbn2b") in new stack == Using SIP RTP CoS mark 5 Audio is at 113.253.230.26 port 11316 Adding codec 0x8 (alaw) to SDP Adding non-codec 0x1 (telephone-event) to SDP Reliably Transmitting (NAT) to 203.80.89.139:5060: INVITE sip:13398560848 at s2hkbntel.net:5060...

...and )=CDR(disposition) disagreeing. Below is a dialplan snippet and the resulting CLI output. This is running in an 'h' extension. Noop(DIALSTATUS=${DIALSTATUS}) Noop(CDR(disposition)=${CDR(disposition)}) -- Executing [h at pbxmax-dial-simple:1] NoOp("SIP/msx_01-0000005b", "DIALSTATUS=ANSWER") in new stack -- Executing [h at pbxmax-dial-simple:2] NoOp("SIP/msx_01-0000005b", "CDR(disposition)=NO ANSWER") in new stack Unless I seriously misunderstand the CDR(disposition) function, this looks like a bug to me. Does any else hav...

...00000 0000000000000000 0000000000000000 000021d9 2**0 $ ./bin/llvm-objdump -h a.out | grep debug 27 .zdebug_info 00000058 0000000000000000 28 .zdebug_abbrev 00000053 0000000000000000 29 .zdebug_aranges 00000014 0000000000000000 30 .zdebug_macinfo 00000014 0000000000000000 31 .zdebug_line 0000005b 0000000000000000 32 .zdebug_loc 00000014 0000000000000000 33 .zdebug_pubtypes 00000014 0000000000000000 34 .zdebug_str 00000073 0000000000000000 35 .zdebug_ranges 00000014 0000000000000000 Decompression and proper handling of debug info sections may be needed in llvm-dwarfdump and llvm-sym...

...**0 >> $ ./bin/llvm-objdump -h a.out | grep debug >> 27 .zdebug_info 00000058 0000000000000000 >> 28 .zdebug_abbrev 00000053 0000000000000000 >> 29 .zdebug_aranges 00000014 0000000000000000 >> 30 .zdebug_macinfo 00000014 0000000000000000 >> 31 .zdebug_line 0000005b 0000000000000000 >> 32 .zdebug_loc 00000014 0000000000000000 >> 33 .zdebug_pubtypes 00000014 0000000000000000 >> 34 .zdebug_str 00000073 0000000000000000 >> 35 .zdebug_ranges 00000014 0000000000000000 >> >> Decompression and proper handling of debug info...

...000000 000021d9 > 2**0 > $ ./bin/llvm-objdump -h a.out | grep debug > 27 .zdebug_info 00000058 0000000000000000 > 28 .zdebug_abbrev 00000053 0000000000000000 > 29 .zdebug_aranges 00000014 0000000000000000 > 30 .zdebug_macinfo 00000014 0000000000000000 > 31 .zdebug_line 0000005b 0000000000000000 > 32 .zdebug_loc 00000014 0000000000000000 > 33 .zdebug_pubtypes 00000014 0000000000000000 > 34 .zdebug_str 00000073 0000000000000000 > 35 .zdebug_ranges 00000014 0000000000000000 > > Decompression and proper handling of debug info sections may be needed &...

...ase. I believe I found the cause while looking at the asterisk logs. I am finding hundreds of entries like this when they report audio problems. [08/19 15:04:17.176] DEBUG[4062][C-00000076] res_timing_timerfd.c: Expected to acknowledge 1 ticks but got 4 instead [08/19 15:04:17.173] DEBUG[4008][C-0000005b] res_timing_timerfd.c: Expected to acknowledge 1 ticks but got 3 instead [08/19 15:04:17.180] DEBUG[4008][C-0000005b] res_timing_timerfd.c: Expected to acknowledge 1 ticks but got 2 instead [08/19 15:04:17.174] DEBUG[3933][C-00000038] res_timing_timerfd.c: Expected to acknowledge 1 ticks but got 2...

.../llvm-objdump -h a.out | grep debug >>> 27 .zdebug_info 00000058 0000000000000000 >>> 28 .zdebug_abbrev 00000053 0000000000000000 >>> 29 .zdebug_aranges 00000014 0000000000000000 >>> 30 .zdebug_macinfo 00000014 0000000000000000 >>> 31 .zdebug_line 0000005b 0000000000000000 >>> 32 .zdebug_loc 00000014 0000000000000000 >>> 33 .zdebug_pubtypes 00000014 0000000000000000 >>> 34 .zdebug_str 00000073 0000000000000000 >>> 35 .zdebug_ranges 00000014 0000000000000000 >>> >>> Decompression and proper...

...grep debug > >>> 27 .zdebug_info 00000058 0000000000000000 > >>> 28 .zdebug_abbrev 00000053 0000000000000000 > >>> 29 .zdebug_aranges 00000014 0000000000000000 > >>> 30 .zdebug_macinfo 00000014 0000000000000000 > >>> 31 .zdebug_line 0000005b 0000000000000000 > >>> 32 .zdebug_loc 00000014 0000000000000000 > >>> 33 .zdebug_pubtypes 00000014 0000000000000000 > >>> 34 .zdebug_str 00000073 0000000000000000 > >>> 35 .zdebug_ranges 00000014 0000000000000000 > >>> > >&gt...

...ay, here's the output, please let me know if it means anything to anyone! Thanks, Adam. Assertion failure in __journal_unfile_buffer() at transaction.c:1522: "jh->b_jlist < 9" invalid operand: 0000 CPU: 0 EIP: 0010:[<c015d730>] Not tainted EFLAGS: 00010286 eax: 0000005b ebx: cfa42c40 ecx: cfb34000 edx: 00000000 esi: c84784b0 edi: 00000000 ebp: c84784e0 esp: cfb35e64 ds: 0018 es: 0018 ss: 0018 Process kjournald (pid: 30, stackpage=cfb35000) Stack: c0250c80 c0251296 c0250c60 000005f2 c0251286 c5172640 c84784b0 cfa42c40 c015e27d c84784b0 cfae4...

Hi Holger, > Note that I did specify "-g", but not any "-Ox" switches. That > made the size of all *.o files together being 143 MB. LLVM represents debug info as explicit calls to intrinsics. This approach has many advantages, but a possible disadvantage is that it can significantly increase the size of the bitcode. I don't know if that explains your observations.

...: e1c7bde0 ebp: 0000145b esp: e1c7bd90 Jan 31 18:13:04 webserver kernel: ds: 007b es: 007b ss: 0068 Jan 31 18:13:04 webserver kernel: Process popper (pid: 23878, threadinfo=e1c7b000 task=f7428eb0) Jan 31 18:13:04 webserver kernel: Stack: 00000000 e1c7bdd8 e1c7bde0 0000145b c014107c f7f42e00 0000005b 00000000 Jan 31 18:13:04 webserver kernel: b7ff405b 00000fa5 e1f88998 f88d3820 e1f88a48 edb09280 00000001 e1c7bef8 Jan 31 18:13:04 webserver kernel: 00000000 e1c7bebc 00000000 2f000000 00000000 00000000 e1c7be0c 00000000 Jan 31 18:13:04 webserver kernel: Call Trace: Jan 31 18:13:04 we...

...CONTENTS, READONLY, DEBUGGING 9 .debug_pubnames 00000089 00000000 00000000 000027d8 2**0 CONTENTS, RELOC, READONLY, DEBUGGING 10 .debug_aranges 00000020 00000000 00000000 00002861 2**0 CONTENTS, RELOC, READONLY, DEBUGGING 11 .debug_str 0000005b 00000000 00000000 00002881 2**0 CONTENTS, READONLY, DEBUGGING 12 .comment 0000003a 00000000 00000000 000028dc 2**0 CONTENTS, READONLY 13 .note.GNU-stack 00000000 00000000 00000000 00002916 2**0 CONTENTS, READONLY When I compi...

...>>> 27 .zdebug_info 00000058 0000000000000000 >> >>> 28 .zdebug_abbrev 00000053 0000000000000000 >> >>> 29 .zdebug_aranges 00000014 0000000000000000 >> >>> 30 .zdebug_macinfo 00000014 0000000000000000 >> >>> 31 .zdebug_line 0000005b 0000000000000000 >> >>> 32 .zdebug_loc 00000014 0000000000000000 >> >>> 33 .zdebug_pubtypes 00000014 0000000000000000 >> >>> 34 .zdebug_str 00000073 0000000000000000 >> >>> 35 .zdebug_ranges 00000014 0000000000000000 >> >&...

I want to share a little LLVM experiment. I tried LLVM on one of my bigger Qt 3.x based projects. I used llvm from SVN trunk (r39999) and SVN llvm-gcc-4.01 (r370) and did compile every file with /usr/src/llvm/dist/bin/g++ -c -pipe -g \ -Wall -Wextra -Wno-sign-compare \ ... lots of -Dxxxx ... \ --emit-llvm -I/usr/share/qt3/mkspecs/default \ -I. -I.. -I../../../include/qt3 -I.obj/ \

...ed <wine-loader> Threads: process tid prio (all id:s are in hex) 0000000e 00000014 0 00000010 0 0000000f 0 00000011 00000016 0 00000013 0 00000012 0 00000017 00000018 0 0000003d 00000038 0 00000044 0 0000008f 0 000000df 0 000000db 0000005b 0 0000000d 0 000000b3 0 0000002c 0 000000cc 0 00000082 0 0000007f 0 00000077 0 00000030 -1 000000a7 0 00000048 -1 00000020 0 00000090 -1 0000005e -1 00000042 -1 000000d2 -1 00000060 -1 0000004f -1 00000035 -1 00000040 -1 0000007c...

...00000046 00000047 0 0000000b 0000000d 0 0000000c 00000048 0 00000049 0000004a 0 0000004b 0000004c 0 0000004d 0000004e 0 0000004f 00000050 0 00000051 00000052 0 00000053 00000054 0 00000055 00000056 0 00000057 00000058 0 00000059 0000005a 0 0000005b 0000005c 0 0000005d 0000005e 0 0000005f 00000060 0 00000061 00000062 0 00000063 00000064 0 00000065 (D) C:\windows\system32\winedbg.exe 00000066 0 <== Backtrace: =>0 0x00000000 (0x0033f118) 1 0x7ec886c3 in user32 (+0x586c3) (0x0033f1e8) 2 0x7ec8939e in user32...

...0 00000031 0 00000030 0 0000002f 0 0000002e 0 0000002d 0 0000002c 0 0000002b 0 0000002a 0 0000004c (D) C:\Programme\GOG.com\Baldurs Gate\bgmain2.exe 00000062 2 <== 0000005c 0 0000005b 0 00000028 15 00000042 0 0000004d 0 Backtrace: =>0 0x007d006e in bgmain2 (+0x3d006e) (0x00dbbbe0) 1 0x008bb128 (0x008bb088) 2 0x01d70038 (0x008bb098) 3 0x008bb088 (0x00d09258) 4 0x008bb098 (0x008bb0a8) 5 0x00d09258 (0x00b3f1c8) 6 0x008bb0a8 (0x00b31...

...ld-linux.so.2 Threads: process tid prio (all id:s are in hex) 0000000c 00000012 0 0000000e 0 0000000d 0 0000000f 00000016 0 00000015 0 00000011 0 00000010 0 00000017 00000018 0 00000020 (D) C:\Program Files\Steam\Steam.exe 00000060 0 0000005c 0 0000005b 0 0000005a 0 00000059 1 00000058 0 00000057 0 00000056 0 00000055 1 00000054 0 00000053 1 00000052 0 00000051 1 00000050 0 0000004f 1 0000004e 0 0000004d 1 0000004c 0 0000004b 1 0000004a 0 00000049 1 00000048 0 00000013...

...00000033 0 00000032 0 00000031 0 0000002f 0 00000028 rpcss.exe 00000066 0 00000027 0 00000026 0 00000024 0 00000023 0 00000029 DMXControl.exe 0000005d 0 00000050 0 00000057 0 0000004d 0 00000063 0 00000053 0 0000002c 0 0000000b 0 0000005b 0 00000064 0 00000015 0 00000061 0 00000025 0 00000055 0 00000058 0 00000067 0 00000059 0 00000062 0 00000056 0 00000060 0 00000065 0 0000005c 0 0000005e 0 0000005a 0 00000054 0 0000005f 0 0000004e 0 0000002a 0 00000019...