9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] acid:V: line in mkfile for pc64
Date: Fri, 29 Jan 2021 14:41:59 +0100	[thread overview]
Message-ID: <6E1A501481850A7829B9B9DF58041B3C@felloff.net> (raw)
In-Reply-To: <4E3B69E98B663791E1EAB73ACDBDE6CA@hera.eonet.ne.jp>

hey kenji!

is it possible for you to make a picture of the crash?

with ktrace -i we can get a better backtrace. as the
places you put do not make much sense. but this is
normal as the kernel just prints every stack location
that looks like a pointer into the kernel text. it
might actually just be left over data in uninitialized
variables from previous call chains.

ktrace knows the call frame sizes from the debug symbols,
and skips the false text addresses. with the -i flag,
it will interactively ask you for the stack locations
of the next return pc.

--
cinap

       reply	other threads:[~2021-01-30  4:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4E3B69E98B663791E1EAB73ACDBDE6CA@hera.eonet.ne.jp>
2021-01-29 13:41 ` cinap_lenrek [this message]
2021-01-30  1:00   ` kokamoto
2021-01-30  1:17     ` kokamoto
2021-02-08  4:35       ` kokamoto
2021-01-27  0:12 kokamoto
2021-01-28 12:57 ` cinap_lenrek

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=6E1A501481850A7829B9B9DF58041B3C@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.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 NNTP newsgroup(s).