search for: config_debug_info

...c.git;a=commit;h=f24c4d725f5b178d1027dca14203f57e8e78a34d Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 19 Feb 2019 02:31:39 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 19 Feb 2019 02:31:39 +0000 [klibc] klcc: Enable stripping even if CONFIG_DEBUG_INFO is enabled klcc should strip its output if the -s option is used, regardless of whether klibc is stripped. Use the standard $(STRIP) instead of $(KLIBCSTRIP) as the strip command. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- klcc/Kbuild | 2 +- 1 file changed, 1 insertion(+)...

...00:14:40 +0000 [klibc] Kbuild: Add option to install unstripped binaries The .deb and RPM packaging tools can automatically split debugging symbols into a separate package. This requires that binaries and shared libaries are initially installed unstripped, and that they are given build IDs. If CONFIG_DEBUG_INFO is defined: * Add --build-id=sha1 to the linker options * Don't strip binaries after linking them Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- defconfig | 1 + scripts/Kbuild.klibc | 6 +++++- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/defcon...

Hi all I used kernel-3.10.68-11.el6 as dom0 and config kdump I have got vmcore file when compute crash, but not found debuginfo package from http://debuginfo.centos.org/ I found kernel-3.10.68-11.el6 set CONFIG_DEBUG_INFO=n Why not set this key? Is there any other method to debug when compute crash Best Wishes Ding -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20160119/dd1cb396/attachment-0002.html>

All, I am running into a situation in which one of my ext3 filesystems is getting hung during normal usage. There are three ext3 filesystems on a CompactFLASH. One is mounted as / and one as /tmp. In my test, I am copying a 100 MB file from /root to /tmp repeatedly. While doing this test, I eventually see the copying stop, and any attempts to access /tmp fail - if I even do ls /tmp the

...ous system calls on alpha. It fixes build failures with an out-of-tree build, or with CONFIG_KLIBC_ZLIB disabled. The shared library now works on ia64. This release also enables building executables and libraries with full debug information, and adds the option to install them without stripping (CONFIG_DEBUG_INFO). A git shortlog of changes since version 2.0.5 follows. Ben. Ben Hutchings (13): [klibc] 2.0.5 released, next version is 2.0.6 [klibc] Build and install shared binaries only if KLIBCSHAREDFLAGS is defined [klibc] Build and install kinit and sh without ".shared" suffi...

...2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/defconfig b/defconfig index 9938e0ab..7d46de94 100644 --- a/defconfig +++ b/defconfig @@ -6,5 +6,5 @@ CONFIG_KLIBC_ZLIB=y CONFIG_REGPARM=y # ARM options # CONFIG_KLIBC_THUMB is not set -# CONFIG_AEABI is not set +CONFIG_AEABI=y # CONFIG_DEBUG_INFO is not set

...@@ KLIBCAR := $(AR) # The second will be used for reproducible builds, the first otherwise. klibc-ar = $(KLIBCAR) $(if $(KBUILD_REPRODUCIBLE),$(2),$(1)) -KLIBCRANLIB := $(call klibc-ar,s,Ds) +KLIBCRANLIB := $(RANLIB) $(if $(KBUILD_REPRODUCIBLE),-D) KLIBCSTRIP := $(if $(CONFIG_DEBUG_INFO),true,$(STRIP)) KLIBCNM := $(NM) KLIBCOBJCOPY := $(OBJCOPY)

...k for $(KLIBCKERNELSRC)/include directory [klibc] Simplify build instructions [klibc] README.klibc: Document most of the build options [klibc] REAMDE.klibc: Update architecture status [klibc] arm: Enable CONFIG_ARM_EABI by default [klibc] klcc: Enable stripping even if CONFIG_DEBUG_INFO is enabled [klibc] Kbuild: Work around broken "ar s" in binutils 2.32 [klibc] Fix missing header dependency for sigsuspend.o [klibc] nfsmount: Use kernel client's default value for timeo option Dimitri John Ledkov (1): [klibc] ipconfig: Implement support -d .....

Hi all I used kernel-3.10.68-11.el6 as dom0 and config kdump I have got vmcore file when compute crash, but not found debuginfo package from http://debuginfo.centos.org/ I found kernel-3.10.68-11.el6 set CONFIG_DEBUG_INFO=n Why not set this key? Is there any other method to debug when compute crash Best Xiaoding -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20151225/89c388ce/attachment-0002.html>

I realised my original bug report was for a guest kernel compiled without frame pointers which might be unhelpful, so I enabled CONFIG_DEBUG_INFO and CONFIG_FRAME_POINTER, but I don't think this has made the backtrace any more detailed. Is there anything more I can do to pinpoint what might be going on here? Cheers, Chris. divide error: 0000 [#1] PREEMPT SMP Modules linked in: CPU: 1 PID: 1013 Comm: mkdir Not tainted 3.14.4-guest #...

...or + strerror(). If disabled, strerror() returns the error number as a + string. +* CONFIG_KLIBC_ZLIB (bool): Include zlib decompression functions. If + disabled, kinit can only load uncompressed ramdisk images. +* CONFIG_KLIBC_ZIP (bool): Include compression support in the gzip + command. +* CONFIG_DEBUG_INFO (bool): Install all executables and the shared + library with debug information and build IDs included. If + disabled, the executables and shared library are stripped when + installed. + +For arm only: + +* CONFIG_KLIBC_THUMB (bool): Compile all code to Thumb instructions, + which should reduc...

...http://bugs.freedesktop.org/attachment.cgi?id=29219) kernel log I have been getting this NULL pointer dereference since drm-next was merged to nouvuea/linux-2.6 master on August 21. The card is a GeForce GTX 275 (NVA0) The dereference does not happen in the following circumstances. 1. kernel has CONFIG_DEBUG_INFO=y 2. booting with kms disabled and then reloading the module with modeset=1 What other information should I provide to help figure this out? bisecting is difficult due to the drm-next merge. The attached trace is with current master (e02aed2) -- Configure bugmail: http://bugs.freedesktop.org/u...

https://bugs.freedesktop.org/show_bug.cgi?id=31058 Summary: Flickering area on external monitor [9400M] Product: xorg Version: git Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Paolo Bonzini <pbonzini at redhat.com> wrote: > Il 29/05/2014 19:45, Chris Webb ha scritto: >> Chris Webb <chris at arachsys.com> wrote: >> >>> My CPU flags inside the crashing guest look like this: >>> >>> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush >>> mmx fxsr sse sse2 ht syscall nx mmxext

Paolo Bonzini <pbonzini at redhat.com> wrote: > Il 29/05/2014 19:45, Chris Webb ha scritto: >> Chris Webb <chris at arachsys.com> wrote: >> >>> My CPU flags inside the crashing guest look like this: >>> >>> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush >>> mmx fxsr sse sse2 ht syscall nx mmxext

https://bugs.freedesktop.org/show_bug.cgi?id=28763 Summary: Kernel Oops when displaying a large image Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

...set +# CONFIG_SLUB_STATS is not set +# CONFIG_DEBUG_RT_MUTEXES is not set +# CONFIG_RT_MUTEX_TESTER is not set +# CONFIG_DEBUG_SPINLOCK is not set +CONFIG_DEBUG_MUTEXES=y +# CONFIG_DEBUG_SPINLOCK_SLEEP is not set +# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set +# CONFIG_DEBUG_KOBJECT is not set +# CONFIG_DEBUG_INFO is not set +# CONFIG_DEBUG_VM is not set +# CONFIG_DEBUG_WRITECOUNT is not set +CONFIG_DEBUG_MEMORY_INIT=y +# CONFIG_DEBUG_LIST is not set +# CONFIG_DEBUG_SG is not set +# CONFIG_DEBUG_NOTIFIERS is not set +# CONFIG_BOOT_PRINTK_DELAY is not set +# CONFIG_RCU_TORTURE_TEST is not set +# CONFIG_RCU_CP...

...set +# CONFIG_SLUB_STATS is not set +# CONFIG_DEBUG_RT_MUTEXES is not set +# CONFIG_RT_MUTEX_TESTER is not set +# CONFIG_DEBUG_SPINLOCK is not set +CONFIG_DEBUG_MUTEXES=y +# CONFIG_DEBUG_SPINLOCK_SLEEP is not set +# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set +# CONFIG_DEBUG_KOBJECT is not set +# CONFIG_DEBUG_INFO is not set +# CONFIG_DEBUG_VM is not set +# CONFIG_DEBUG_WRITECOUNT is not set +CONFIG_DEBUG_MEMORY_INIT=y +# CONFIG_DEBUG_LIST is not set +# CONFIG_DEBUG_SG is not set +# CONFIG_DEBUG_NOTIFIERS is not set +# CONFIG_BOOT_PRINTK_DELAY is not set +# CONFIG_RCU_TORTURE_TEST is not set +# CONFIG_RCU_CP...

Hi, --- background ---------------------------------------------------- * what the makedumpfile is: To shorten the size of the dumpfile and the time of creating the dumpfile, makedumpfile copies only the necessary pages for analysis to the dumpfile from /proc/vmcore. You can specify the kind of unnecessary pages with dump_level. If you want to shorten the size further, enable the

..._DEBUG_SPINLOCK is not set CONFIG_DEBUG_MUTEXES=y # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_LIST is not set CONFIG_FRAME_POINTER=y # CONFIG_FORCED_INLINING is not set # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_LKDTM is not set # CONFIG_FAULT_INJECTION is not set CONFIG_EARLY_PRINTK=y # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_DEBUG_ST...