similar to: Can't attach to running processes with GDB

1. I noticed the WITHOUT_SSP switch in src.conf(5). Does this mean that Propolice is currently used by default? 2. For debugging purposes, I'd like to rebuild my whole world with debugging symbols. Adding -g to the flags in make.conf seemed to do the trink until right before the installation of the new files. Doing a nm on libc.so.7 yielded all the symbols, as expected. However, after

If you are trying to debug a core dump from a different machine, how do you tell gdb where to look for the debug info files to match the shared libs that you have in a non-standard location? It finds the shared libs themselves with a 'set solib-absolute-path' directive, but it doesn't look for the corresponding (relative) usr/lib/debug/... file that you get if you extract the

ok I know this isn't realy a samba issue but I'm trying to gather some debug info on winbindd for the samba development guys, but I can't compile gdb 5.x or 6.0 on my solaris 9 box! Every other compile problem I've come across I've resolved by searching through google but not this time. If anyone can help I'd realy appreciate it, problem is (using gcc 3.3.2) gcc -g -O2

I'm having a curious issue with LLD/x86_64 linux/elf (Ubuntu 14.04); Where the l_addr of the link_map is invalid when linked with lld, but is fine with gnu ld. I'm using the libgc (boehm) code which when initializing reads the DYNAMIC/DEBUG link_map data, and crashes because the l_addr field has value out of readable memory. The strange this is that it happens only on some linux

Following patch improves integration with kbuild. With a future kernel (2.6.14-rc) it now has working support for 'make clean'. Included is an example of how to compile an early userspace program. I selected gzip as the most simple one for this - and left out all the links to different names (gunzip etc.) Before proceeding with this I need some inputs on what functionality is required by

On Wed, Sep 15, 2004 at 10:48:02AM +0930, Alan Modra wrote: > After using SHAREDFLAGS = -Ttext 0x0f000200 on ppc64 (which I see you > suggested in another email), I see the problem you're talking about. > > klibc is fundamentally broken on ppc64. You just can't call into > another chunk of code (klibc.so in this case) which has a separate toc > and expect things to

Commit-ID: 47e429ec6c758b98a00e69df541448942c6f3ba3 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=47e429ec6c758b98a00e69df541448942c6f3ba3 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 19 Jan 2019 22:47:18 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 19 Jan 2019 22:51:00 +0000 [klibc] Build and install shared

This fixes a long standing issue where it was not possible to do "make usr/klibc/arch/x86_64/longjmp.o" in the kernel. The principle is that all .o files to be part of klibc are listed with klib-y. For each directory a klib.list file is made that specify all .o file and the final AR then adds all .o files to create libc.a. This patch introduce the infrastructure and converts x86_64 to

The *.shared targets require -shared on powerpc, and -R leads to linker errors. This patch makes the -R an arch define. ia64 at least requires -R. --- ash/Makefile +++ ash/Makefile 2003/11/27 15:04:02 @@ -36,7 +36,7 @@ $(STRIP) $(PROG) $(PROG).shared: $(OBJS) $(LIBS) - $(LD) $(LDFLAGS) -o $(PROG).shared -e main $(KLIBSRC)/interp.o $(OBJS) -R $(KLIBSRC)/libc.so $(LIBGCC) + $(LD) $(LDFLAGS)

Hi List, I''d compiled Xen-3.0.3-testing (changeset 11740) on Suse 10.0 Enterprise Server. The compilation succeeded without any errors but the mkinitrd command fails(???) The initrd is being created but when loading the xen kernel, I get the following message repeatedly: "azx_get_reponse() timeout" after pressing ^c the computer continue to run... Then, when I start a gnome

Halo, I think the following patch is correct. I just downloaded 1.0.9 and has the same problem namely it doesn't respect INSTALLROOT when installs the shared library -------------- next part -------------- diff -ur orig/klibc-1.0.8/klcc.in klibc-1.0.8/klcc.in --- orig/klibc-1.0.8/klcc.in 2005-03-07 23:44:49.000000000 +0200 diff -ur orig/klibc-1.0.8/klibc/Makefile klibc-1.0.8/klibc/Makefile

Hello, I'm seeing a segfault in the imap process with the current mercurial tip (including changeset 17382 e99cd21e1f92) when selecting a particular virtual mail folder (but no other virtual mailboxes) and then selecting a different mail folder as in the IMAP transcript below. The same segfaults are triggered with IMAP clients. The situation is worse with the 2.2.13 which segfaults when

>>>>> Georgi Boshnakov >>>>> on Wed, 9 Sep 2020 10:48:56 +0000 writes: > I think that this is because `[<-` dispatches on S4 > methods only if the first argument is S4. ?"[<-" says: > "These operators are also implicit S4 generics, but as > primitives, S4 methods will be dispatched only on S4 > objects

Seems there is some breakage with -hg latest - 2.2.16 (86f535375750+). I've just had 4 core files created in short succession on both servers in the replication set. Here's the first... tornado reuben # gdb /usr/libexec/dovecot/imap core GNU gdb (Gentoo 7.9 vanilla) 7.9 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Commit-ID: 81b7c464c5db568edf894bacfc9bee2cec837367 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=81b7c464c5db568edf894bacfc9bee2cec837367 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Fri, 25 Jan 2019 00:40:19 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:37:55 +0000 [klibc] Fix errlist.c generation

Commit-ID: 9d8d648e604026b32cad00a84ed6c29cbd157641 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=9d8d648e604026b32cad00a84ed6c29cbd157641 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 29 Feb 2020 00:03:20 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 29 Feb 2020 00:11:26 +0000 [klibc] Kbuild: Tell gas we

Commit-ID: 312b3d0a38ff2e43becd47cf1f4a930bc0c4b8e6 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=312b3d0a38ff2e43becd47cf1f4a930bc0c4b8e6 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 29 Apr 2020 22:24:33 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 17:33:29 +0100 Revert "[klibc] Kbuild: Tell

Commit-ID: c562319cdba0102c3a8a8298ba94e645418193d5 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=c562319cdba0102c3a8a8298ba94e645418193d5 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 29 Apr 2020 22:28:10 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 17:33:29 +0100 [klibc] Kbuild: Add a

On 04/28/2015 01:42 PM, Reuben Farrelly wrote: > Seems there is some breakage with -hg latest - 2.2.16 (86f535375750+). I've just had 4 core files created in short succession on > both servers in the replication set. Here's the first... Does it work with 1081d57b524e or later? br, Teemu Huovila > tornado reuben # gdb /usr/libexec/dovecot/imap core > GNU gdb (Gentoo 7.9

W dniu 23.09.2015 o 15:30, Timo Sirainen pisze: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.19.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.19.rc1.tar.gz.sig > > A lot of changes since v2.2.18, so here's a release candidate first. If no bugs are reported, I'm planning on making the final release sometimes this week. The most interesting new features here