search for: gdb's

Fancy, while not fun. :-) But thanks, that does work. Doing that, n?ing over calls to strcmp, it failed: passdbs_init () at passdb.c:313 313 passdb_register_module(&passdb_ldap); (gdb) passdb_register_module (iface=0x280120) at passdb.c:33 33 old_iface = passdb_interface_find(iface->name); (gdb) passdb_interface_find (name=0x16fe60 "ldap") at passdb.c:20 20 array_foreach(&passdb_interfaces, ifaces) { (gdb) 21 struct passdb_module_interface *iface = *iface...

Thanks! This is in regards to bug 3084, I am trying to find out why samba is crashing. I am using glibc-2.4 with nptl threads. It seems to be a memory or threading issue. Thanks for any help. Running smbd through gdb: Breakpoint 6, charset_name (ch=CH_DISPLAY) at lib/charcnv.c:57 57 const char *ret = NULL; (gdb) Continuing. Substituting charset 'ANSI_X3.4-1968' for LOCALE Breakpoint 2, smb_iconv_close (cd=0x8412a28) at lib/iconv.c:315 315 if (cd->cd_direct) iconv_close((ico...

...table (with different column numbers). This can be confusing to debuggers > that ignore column info, or possibly to the users who expect “set breakpoint > on line 12” to set one breakpoint and it actually sets 4. “How come nothing > happens when I hit Continue?” Yes. David is testing the gdb testsuite to see whether that's a real problem. If that's a problem, it should show there (since GCC does not emit column info in dwarf, AFAIR). In any case, that would be a debugger issue. Not compiler. > For –Rpass and related uses, it might be useful to distinguish between > _tr...

Okay. Got to the next bit pretty quickly.: Breakpoint 4, auth_settings_read (service=0x0, pool=0x4104b020, output_r=0x7fdfffff6d0) at auth-settings.c:522 522 input.module = "auth"; (gdb) n 523 input.service = service; (gdb) n 524 if (master_service_settings_read(master_service, &input, (gdb) s Program received signal SIGTRAP, Trace/breakpoint trap. Cannot remove breakpoints because program is no longer writable. It might be running in another process. Further execution is p...

Sadly, that doesn?t help either. Over the past day, I?ve built and installed a different branch of the OS (stable/11, instead of release/11.1), to see if a new compiler/libc might change things. Sadly, it does not. In the same situation now, auth fails immediately with signal 11. Running gdb on auth (from build dir, compiled -g -O2) shows something similar. - Chris # gdb work/dovecot-2.2.33.2/src/auth/.libs/auth GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it...

...<dpatel at apple.com> wrote: > > On Mar 29, 2011, at 7:29 PM, Talin wrote: > >> I've been trying to track down the problem with the DWARF info that is being emitted by my front end, which has been broken for about a month now. Here's what happens when I attempt to use gdb to debug one of my programs on OS X: >> >> gdb stack crawl at point of internal error: >> [ 0 ] /usr/libexec/gdb/gdb-i386-apple-darwin (align_down+0x0) [0x122300] >> [ 1 ] /usr/libexec/gdb/gdb-i386-apple-darwin (find_partial_die_in_comp_unit+0x65) [0xc0e19] >> [ 2 ] /...

...patel at apple.com> wrote: > > On Mar 29, 2011, at 7:29 PM, Talin wrote: > > I've been trying to track down the problem with the DWARF info that is > being emitted by my front end, which has been broken for about a month now. > Here's what happens when I attempt to use gdb to debug one of my programs on > OS X: > > gdb stack crawl at point of internal error: > [ 0 ] /usr/libexec/gdb/gdb-i386-apple-darwin (align_down+0x0) [0x122300] > [ 1 ] /usr/libexec/gdb/gdb-i386-apple-darwin > (find_partial_die_in_comp_unit+0x65) [0xc0e19] > [ 2 ] /usr/libexec...

This bot seems kind of flaky. In the last 100 builds, it has failed "gdb-75-check" 22 times with what is either a linker error or a missing header (or both?): gdb compile failed, /usr/bin/ld: error: /home/buildslave/osuosl_slave/clang-x86_64-ubuntu-gdb-75/clang-tests/build/gdb/testsuite/gdb.trace/pendshr1.c.o: requires dynamic R_X86_64_PC32 reloc against '...

...(114808, max=2928) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 >>> dyld: fast lazy bind offset out of range (114808, max=2928) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 >>> >>> with... >>> >>> (gdb) break *0x100ebb3a0 >>> Breakpoint 2 at 0x100ebb3a0 >>> >>> this lands me at... >>> >>> dyld: weak bind: LLVMPolly.so:0x1010F4BD0 = libc++.1.dylib:__Znwm, *0x1010F4BD0 = 0x7FFF898BD0DF >>> >>> Breakpoint 2, 0x0000000100ebb3a0 in pch_...

I'm trying to follow the example in the R for Windows FAQ on running gdb and am getting stuck because gdb tells me "Cannot access memory at address ...". Here's what my gdb session looks like (This one from a cygwin shell, but same results from plain Windows CMD shell): $ cd R-devel/src/gnuwin32 $ gdb ../../bin/Rgui.exe GNU gdb 5.2.1 Copyright 2002 Free...

Hi, On 06-Dec-16 10:10, Aki Tuomi wrote: > Alternatively if you could try and print the args array in cmd_search? > > f 14 > p args[0] > p args[1] > ... > until NULL My hand got sore at first 100 and they are below. I will mail you the binary and core in seperate mail. (gdb) f 14 #14 0x08058219 in cmd_search (cmd=0x85e1800) at cmd-search.c:42 42 ret = imap_search_args_build(cmd, args, charset, &sargs); (gdb) p args[0] $1 = {type = IMAP_ARG_ATOM, parent = 0x0, str_len = 3, _data = {str = 0x85e40f8 "ALL", literal_size = 140394744, list = {arr...

I'm having trouble debugging x86 code generated by LLVM. GDB does work with the code, but not correctly, for example, the "next" command does not skip over a function call. Here's an example. Source program gdb1.c: int x; void foo(){ x++; } void bar(){ x--; } int main(){ foo(); bar(); return 0; } commands: $ llvm-gcc -g -emit-...

The gdb developers are rapidly approaching the release of gdb 7.0 (which will be required to debug optimized code generated by gcc 4.5 due changes related to the var tracking association merge and other code). They currently have patches proposed that allows gdb 7.0 to debug code in darwin9.6. However the...

...et out of range (114808, max=2928) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 > > dyld: fast lazy bind offset out of range (114808, max=2928) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 > > > > with... > > > > (gdb) break *0x100ebb3a0 > > Breakpoint 2 at 0x100ebb3a0 > > > > this lands me at... > > > > dyld: weak bind: LLVMPolly.so:0x1010F4BD0 = libc++.1.dylib:__Znwm, *0x1010F4BD0 = 0x7FFF898BD0DF > > > > Breakpoint 2, 0x0000000100ebb3a0 in pch_address_space () >...

...for amd64: http://yziquel.homelinux.org/debian/pool/main/o/ocaml-r/ Some documentation (not entirely up to date...): http://yziquel.homelinux.org/topos/api/ocaml-r/R.html http://yziquel.homelinux.org/topos/debian-ocamlr.html Back to my segfault: > yziquel at seldon:~/git/ocaml-finquote$ gdb -silent -d /home/yziquel/src/r-base-2.10.1/src/main/ _build/test/test.native > Reading symbols from /home/yziquel/git/ocaml-finquote/_build/test/test.native...(no debugging symbols found)...done. > (gdb) run > Starting program: /home/yziquel/git/ocaml-finquote/_build/test/test.native >...

Hi! It's indeed better to open a new thread for this. So, here's my test session: $ qemu -fda extlinux.144 -s -S Then in another terminal: $ gdb extlinux.elf (gdb) set architecture i8086 (gdb) target remote localhost:1234 Remote debugging using localhost:1234 0x0000fff0 in ?? () at localboot.inc:68 68 jmp kaboom ; If we returned, oh boy... How does "jmp kaboom" get here? We are at the BIOS entry point: (gdb) display/10i $c...

I've been trying to track down the problem with the DWARF info that is being emitted by my front end, which has been broken for about a month now. Here's what happens when I attempt to use gdb to debug one of my programs on OS X: gdb stack crawl at point of internal error: [ 0 ] /usr/libexec/gdb/gdb-i386-apple-darwin (align_down+0x0) [0x122300] [ 1 ] /usr/libexec/gdb/gdb-i386-apple-darwin (find_partial_die_in_comp_unit+0x65) [0xc0e19] [ 2 ] /usr/libexec/gdb/gdb-i386-apple-darwin (find_p...

On 06.12.2016 09:32, Toni Mattila wrote: > Hi, > > On 05-Dec-16 20:28, Toni Mattila wrote: >> Panicing stopped when all index files where deleted. > > It happens again in same user account, so rebuilding indexes didn't > fix it. > > Here's bt full instead of just bt: > #0 0x001d4402 in __kernel_vsyscall () > No symbol table info available. > #1

On Mar 29, 2011, at 7:29 PM, Talin wrote: > I've been trying to track down the problem with the DWARF info that is being emitted by my front end, which has been broken for about a month now. Here's what happens when I attempt to use gdb to debug one of my programs on OS X: > > gdb stack crawl at point of internal error: > [ 0 ] /usr/libexec/gdb/gdb-i386-apple-darwin (align_down+0x0) [0x122300] > [ 1 ] /usr/libexec/gdb/gdb-i386-apple-darwin (find_partial_die_in_comp_unit+0x65) [0xc0e19] > [ 2 ] /usr/libexec/gdb/gdb-...

...Breakpoint 1, mp_register_ioapic (id=0, address=4273995776, gsi_base=0, cfg=0xc1b2fe88 <init_thread_union+7816>) at arch/x86/kernel/apic/io_apic_b.c:389 389 bool hotplug = !!ioapic_initialized; 1: x/i $pc => 0xc10469c7 <mp_register_ioapic+23>: mov    0xc1d36170,%eax 2: gsi_base = 0 (gdb) ni 393 pr_warn("%s, %d %x %x %px\n", __func__, id, address, gsi_base, cfg); 1: x/i $pc => 0xc10469cc <mp_register_ioapic+28>: mov    %eax,0x18(%esp) 2: gsi_base = 0 (gdb)  0xc10469d0 393 pr_warn("%s, %d %x %x %px\n", __func__, id, address, gsi_base, cfg); 1: x/i $pc...