search for: disass

...cc00464d10 in ?? () (gdb) bt #0 0x00002acc00464d10 in ?? () #1 0x00002acc1869f026 in ?? () #2 0x000000000074eb10 in ?? () #3 0x000000000074eb10 in ?? () #4 0x0000000000000000 in ?? () This is the jitted function: the last call refers 0x2acc00464d10, while the correct address is 0x464d10 (gdb) disass 0x00002acc1869f010 0x00002acc1869f026 Dump of assembler code from 0x2acc1869f010 to 0x2acc1869f026: 0x00002acc1869f010: push %r14 0x00002acc1869f012: push %rbx 0x00002acc1869f013: sub $0x8,%rsp 0x00002acc1869f017: mov $0x7f0ed0,%edi 0x00002acc1869f01c: callq 0x2acc173...

This fixes a segmentation fault in the system call's error handling path with dynamically-linked binaries on PowerPC64 little endian. The system call stub wasn't loading up r2 with the appropriate TOC value in its global entry point. The r2 setup code comes from the FUNC_START macro in gcc [1] and an equivalent one can also be found in the LOCALENTRY macro in glibc [2]. On the ELFv2 ABI

...lrefs -A20 sectname __objc_selrefs segname __DATA addr 0x00003034 size 0x00000018 offset 8244 align 2^2 (4) reloff 0 nreloc 0 flags 0x10000005 reserved1 0 reserved2 0 Now, obviously these are where the selectors are, and sure enough when I start walking the disass I find these addresses coming up.. but if I look at address 0x3034 I don't see 00002fec or anything the like.., in fact, using 0xED, I see 68300000 at offset 0x3034... so, where are the selectors? Am I missing something, how is this section used?? Any help, pointers would be great, thanks! -...

...n Centos4. I can make it work on Centos5 and that's great. I just need to figure out a way to reproduce the problem on a small test case. The specific problem is that when I throw an exception, I get a segfault. It only happens on Centos4, and only on ia-32 machines. In an act of desparation I disassembled the bit of code that's segfaulting and got this: (gdb) disass Dump of assembler code for function _ZN14__gnu_internal10get_globalEv: 0x08579614 <...get_globalEv+0>: call 0x8577c3e <__i686.get_pc_thunk.cx> 0x08579619 <...get_globalEv+5>: add $0x3b31c7,%ecx 0x0857961...

...and set the right architecture. file bios/core/lpxelinux.elf target remote localhost:1234 #set architecture i8086 set architecture i386 set osabi none Depending whether you're debugging 16 bits or 32 bits code, you will need to set the architecture accordingly. You can switch on the fly if the disass command decode the instructions incorrectly. (At least or worked for me, I use a 32 bits OS.) Note that the order is quite important as gdb is pretty annoying with its "g packet too long" errors. I guess the "set architecture" has to appear after the "target" command....

...1319 { 1320 size_type (&__a)[__n_words] = __r_.first().__r.__words; 1321 for (unsigned __i = 0; __i < __n_words; ++__i) -> 1322 __a[__i] = 0; 1323 } 1324 1325 template <size_type __a> static And: (lldb) disass cryptest.exe`_GLOBAL__sub_I_chacha_avx.cpp at chacha_avx.cpp: 0x10016ec30: pushq %rbp 0x10016ec31: movq %rsp, %rbp 0x10016ec34: pushq %r14 0x10016ec36: pushq %rbx 0x10016ec37: movq 0x24cf8a(%rip), %rax ; (void *)0x00000001003e69f0: vtable for CryptoPP::NullNameValueP...

On Wed, Jan 13, 2016 at 01:22:17AM +0100, Celelibi wrote: > 2016-01-12 22:21 UTC+01:00, Tal Lubko: > > On Mon, Jan 11, 2016 at 07:20:20PM -0500, Shao Miller wrote: > >> > >> Yes, you can print debug-output from custom builds. > >> > > > > Regarding my other question (debugging). > > I know it is possible to use prints for debugging. > > I

...directory. (gdb) where #0 0x200005dbd28 in __kill () at __kill:2 #1 0x200005db9f8 in raise (sig=6) at ../sysdeps/posix/raise.c:27 #2 0x200005dd8b8 in abort () at ../sysdeps/generic/abort.c:88 #3 0x12005b9f4 in smb_panic () #4 0x120042a40 in fault_report () #5 0x120042ad4 in sig_fault () (gdb) disass __kill Dump of assembler code for function __kill: 0x200005dbd20 <__kill>: lda v0,37(zero) 0x200005dbd24 <__kill+4>: callsys 0x200005dbd28 <__kill+8>: bne a3,0x200005dbd30 <__kill+16> 0x200005dbd2c <__kill+12>: ret zero,(ra),0x1 0x200005dbd...

...onse from 136.201.105.4 ( 136.201.105.4 ) Password: session setup failed: code 0 Attached are the following: bugreport.log -- log.smbd showing samba startup, connection and segfault. debug set at 10 gdb.out -- gdb output of the segfault where.out -- gdb "where" on the segfaulted pid disass.out -- gdb "disass" of the last routine in samba before outside routines are called ldif.out -- ldif of the user account (maddenj) I've been testing this with. generated with ldapsearch -LLL -D"root_dn" -W uid=maddenj > ldif.out smb.conf -- conf file If I can provide y...