similar to: Where's the debuginfo?

On 04/03/2015 11:11 AM, Eric Millbrandt wrote: > Specifically, I'm looking for > kernel-debuginfo-3.10.0-229.1.2.el7.x86_64, but the latest debuginfo > file is kernel-debuginfo-3.10.0-123.13.2.el7.x86_64.rpm, which isn't > even the most recent release from 7.0.1406. Is my Google-fu failing me > or is http://debuginfo.centos.org/7/x86_64/ no longer the current > debuginfo

Just a heads up, since I know gkrellm is in EPEL and not in the main CentOS repos. However, something fairly fundamental has changed, as prior to updating, gkrellm worked fine, but now every time I execute gkrellm the kernel panics. I'm going to triage on a different machine, as the panic corrupted at least one system library used by nautilus, but rpm -Va is your friend in these

Hi, Even though I am not running a centos.plus kernel yum wants to install the kernel-debuginfo for it. # yum install --disablerepo=\* --enablerepo=base-debuginfo kernel-debuginfo Loaded plugins: fastestmirror, refresh-packagekit Setting up Install Process Loading mirror speeds from cached hostfile Resolving Dependencies --> Running transaction check ---> Package kernel-debuginfo.x86_64

I want to use systemtap on a 5.3 system but cannot find supporting kernel-PAE-debuginfo or kernel-debuginfo-common packages. Am I being a noob, or do these not exist for the PAE kernel? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20101202/82cc98b8/attachment-0002.html>

Hi all, This patch, though large, simply moves lib/Analysis/DebugInfo.cpp to lib/VMCore/DebugInfo.cpp and include/llvm/Analysis/DebugInfo.h to include/llvm/DebugInfo.h. Why? Because this module has nothing to do with analysis. It simply defines an interface to the debug info MDNodes. In fact, the lib/VMCore/AsmWriter.cpp file performs a layering violation, because it calculates the DWARF tag

Hi! On C7 I enabled the debuginfo repo and ran: debuginfo-install glibc-2.17-55.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.11.3-49.el7.x86_64 libcom_err-1.42.9-4.el7.x86_64 libselinux-2.2.2-6.el7.x86_64 openssl-libs-1.0.1e-34.el7_0.4.x86_64 pcre-8.32-12.el7.x86_64 xz-libs-5.1.2-8alpha.el7.x86_64 zlib-1.2.7-13.el7.x86_64 Loaded plugins: fastestmirror, langpacks Loading mirror speeds

This line in /etc/yum.repos.d/CentOS-Debuginfo.repo baseurl=http://debuginfo.centos.org/$releasever/$basearch/ ?causes commands like ?yum search --enablerepo=* foo? to fail with the obscure error Error: Failed to synchronize cache for repo 'base-debuginfo' Apparently this is because the debug info RPMs aren?t hosted there any more, per the page at the top of the site.

On Jun 27, 2012, at 4:20 PM, Eric Christopher wrote: > > On Jun 27, 2012, at 4:08 PM, Bill Wendling <wendling at apple.com> wrote: > >> Hi all, >> >> This patch, though large, simply moves lib/Analysis/DebugInfo.cpp to lib/VMCore/DebugInfo.cpp and include/llvm/Analysis/DebugInfo.h to include/llvm/DebugInfo.h. >> >> Why? Because this module has

Greetings, If you dont' care about running debuginfo-tests, and don't maintain a bot that runs debuginfo-tests, you can stop reading. I've uploaded a patch [https://reviews.llvm.org/D39605] that changes the way you run debuginfo-tests. Prior to this patch, the way to run them is to clone an external git repository into clang/test and then debuginfo-tests will happen transparently

On Jun 27, 2012, at 4:08 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all, > > This patch, though large, simply moves lib/Analysis/DebugInfo.cpp to lib/VMCore/DebugInfo.cpp and include/llvm/Analysis/DebugInfo.h to include/llvm/DebugInfo.h. > > Why? Because this module has nothing to do with analysis. It simply defines an interface to the debug info MDNodes. In

cmake -G Ninja -DLLVM_ENABLE_PROJECTS="debuginfo-tests" -DLLVM_USE_LINKER=lld -DCMAKE_BUILD_TYPE="Release" -DLLVM_TARGETS_TO_BUILD=X86 -Wno-dev ../llvm &> ../../cmake.log in cmake.log -- Targeting X86 CMake Error at /home/nnelson/Documents/llvm-project/debuginfo-tests/CMakeLists.txt:30 (message):   Cannot run debuginfo-tests without python 3 installed python3

Is anyone else having trouble getting some RPMs from vault? When I navigate to http://vault.centos.org/debuginfo/5/i386/ ...and try to click on (e.g.) kernel-PAE-debuginfo-2.6.18-8.1.3.el5.i686.rpm I get 404 errors (The requested URL /debuginfo/5/i386/kernel-PAE-debuginfo-2.6.18 -8.1.3.el5.i686.rpm was not found on this server). But then if I wait a while and try again, maybe I get it. Is

I'm trying to debug what I believe to be a kernel bug (https://lists.centos.org/pipermail/centos-devel/2016-March/014463.html) and I'm trying to set up systemtap for that. I'm trying to set up systemtap on kernel 3.18.21-17.el6.x86_64 (Xen 4.4.3-10.el6) and it requires the kernel-debuginfo package, however I cannot find anywhere package kernel-debuginfo-3.18.21-17.el6.x86_64.rpm. In

Hi Samba team, Is there a command or a way to build samba-debuginfo rpm from the samba source. I have been through wiki.samba.org, but failed to find out. Explored the Makefile targets, even there I did not find the make target to build debuginfo package or RPM. Thanks in advance for your help. https://wiki.samba.org/index.php/Writing_a_Samba_VFS_Module -> this page mentions to install

The current mitigation for CVE-2018-14634 is a systemtap script mentioned here: https://access.redhat.com/security/cve/cve-2018-14634 It also mentions that one can build a kernel module to distribute to other machines, but in any case one needs the corresponding debuginfo packages to do either. After enabling CentOS-Debug.repo, what I get is:

On 7 March 2016 at 14:42, Johnny Hughes <johnny at centos.org> wrote: > On 03/03/2016 01:22 PM, Thanos Makatos wrote: >> I'm trying to debug what I believe to be a kernel bug >> (https://lists.centos.org/pipermail/centos-devel/2016-March/014463.html) >> and I'm trying to set up systemtap for that. >> >> I'm trying to set up systemtap on kernel

Ok just tried on Win 7 and the same problem occurs. I am building with : cmake -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DLLVM_USE_CRT_RELEASE=MT -DLLVM_ENABLE_TIMESTAMPS=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON -DLLVM_TARGETS_TO_BUILD="ARM;X86" -DPYTHON_EXECUTABLE=$python_exe -DLLVM_BUILD_TESTS=ON -DLLVM_LIT_TOOLS_DIR=C:/cygwin64/bin fwiw compiler-rt is

> On Jan 29, 2015, at 10:20 AM, Zachary Turner <zturner at google.com> wrote: > > I've been working on adding pdb reading support to llvm. This started as a tool for dumping info from a pdb (similar to llvm-dwarfdump), which has been checked in and currently has limited support for dumping pdb. > > There's still more to be done on the pdb dumping tool, but at this

Hi list, I found relevant documentation regarding DebugInfo creation in the LLVM IR bytecode. It can be done for compileunits, functions, and other constructs, with the help of DIBuilder class. However I can't save debug information related to individual llvm::Instructions. I tried DebugLoc, DILocation setting directly with setMetadata(). I tried other ways, for e.g.:

>The pdb reading code relies *very heavily* on Windows APIs can you make shure not to have any windows api stuff in the pdb-reader interface so its easy to - if someone wants to - implement an windows-api independent version (support reading under linux etc.) because the pdb format needs to be analysed anyway for writing pdb information on compile/link (in the future) Am 29.01.2015 um 19:20