From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 51785 invoked by alias); 2 Feb 2018 20:43:11 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 51733 invoked by uid 48); 2 Feb 2018 20:43:05 -0000 From: "dsmith at redhat dot com" To: systemtap@sourceware.org Subject: [Bug kprobes/22772] missing kernel/module debuginfo for custom lt kernel Date: Fri, 02 Feb 2018 20:43:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: kprobes X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dsmith at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-q1/txt/msg00038.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22772 --- Comment #19 from David Smith --- (In reply to ocket8888 from comment #18) > Created attachment 10776 [details] > specfile used to build all kernel packages A Fedora/RHEL kernel specfile is typically the most complicated spec file in the distro (or at least in the top 10). Since the kernel isn't a typical ELF executable, lots of semi-tricky things are done. What would be more useful than the full specfile itself would be a diff bet= ween your specfile and the specfile you started with. If you just added a custom kernel patch for example or use a custom config file, that shouldn't effect= the debuginfo generation. Another thing to try. If you have access to your kernel's rpm build tree, y= ou could look for a vmlinux or vmlinux.debug file and see if one exists that didn't get packaged. --=20 You are receiving this mail because: You are the assignee for the bug.