public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "ocket8888 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug kprobes/22772] missing kernel/module debuginfo for custom lt kernel
Date: Tue, 06 Feb 2018 16:23:00 -0000	[thread overview]
Message-ID: <bug-22772-6586-ZsY5AYAjdK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22772-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=22772

--- Comment #22 from ocket8888 <ocket8888 at gmail dot com> ---
(In reply to David Smith from comment #19)
> (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
> between 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,
> you could look for a vmlinux or vmlinux.debug file and see if one exists
> that didn't get packaged.

Sorry I took so long to respond; I work for Comcast and the Super Bowl is a
very busy time here. I asked the guy who built the kernel what specs he
modified, and he directed me to the "kernel-lt-4.4" and "kernel-ml-4.10"
specfiles. He says the 4.9-lt (the one I'm having issues with) is a combination
of the two, so I uploaded a diff with each of them. I'm not totally sure how
helpful that is, so if you want a diff with a specific, standard kernel just
let me know.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2018-02-06 16:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 18:31 [Bug kprobes/22772] New: " ocket8888 at gmail dot com
2018-02-01 18:52 ` [Bug kprobes/22772] " ocket8888 at gmail dot com
2018-02-01 18:53 ` ocket8888 at gmail dot com
2018-02-01 18:54 ` ocket8888 at gmail dot com
2018-02-01 19:29 ` dsmith at redhat dot com
2018-02-01 19:48 ` fche at redhat dot com
2018-02-01 20:53 ` ocket8888 at gmail dot com
2018-02-01 20:54 ` ocket8888 at gmail dot com
2018-02-01 20:55 ` ocket8888 at gmail dot com
2018-02-01 20:57 ` fche at redhat dot com
2018-02-01 21:02 ` ocket8888 at gmail dot com
2018-02-01 21:06 ` ocket8888 at gmail dot com
2018-02-01 21:07 ` ocket8888 at gmail dot com
2018-02-01 21:17 ` ocket8888 at gmail dot com
2018-02-01 22:38 ` dsmith at redhat dot com
2018-02-02 17:21 ` ocket8888 at gmail dot com
2018-02-02 17:23 ` fche at redhat dot com
2018-02-02 17:55 ` ocket8888 at gmail dot com
2018-02-02 17:56 ` ocket8888 at gmail dot com
2018-02-02 20:43 ` dsmith at redhat dot com
2018-02-06 16:20 ` ocket8888 at gmail dot com
2018-02-06 16:20 ` ocket8888 at gmail dot com
2018-02-06 16:23 ` ocket8888 at gmail dot com [this message]
2018-02-06 18:40 ` dsmith at redhat dot com
2021-08-06  1:28 ` lennordocdoc0921 at gmail dot com
2021-08-06  8:13 ` mark at klomp dot org
2021-08-06 12:07 ` dsmith at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-22772-6586-ZsY5AYAjdK@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).