From: "Frank Ch. Eigler" <fche@redhat.com>
To: Nikolay Borisov <n.borisov@siteground.com>
Cc: systemtap@sourceware.org
Subject: Re: printing kernel backtrace
Date: Sat, 12 Dec 2015 16:01:00 -0000 [thread overview]
Message-ID: <20151212160044.GB21055@redhat.com> (raw)
In-Reply-To: <CAJFSNy6yN6rTv37PRM6SVEc-7=OBNz4p5Er0BmAyT7GZ-7z=kw@mail.gmail.com>
Hi -
> [...]
> So using -d kernel does indeed fix the backtrace.
Good; will see if can add some diagnostics.
> For the sake of completeness I also tried using --ldd which
> according to the help should include debug info for all referenced
> objects (including the kernel) but it doesn't work.
A documentation glitch: --ldd is for shared library dependencies,
so not including the kernel, will fix.
- FChE
prev parent reply other threads:[~2015-12-12 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 12:33 Nikolay Borisov
2015-12-12 14:38 ` Frank Ch. Eigler
2015-12-12 15:37 ` Nikolay Borisov
2015-12-12 16:01 ` Frank Ch. Eigler [this message]
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=20151212160044.GB21055@redhat.com \
--to=fche@redhat.com \
--cc=n.borisov@siteground.com \
--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).