From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] v9fs vs mmap (not quite SOLVED)
Date: Tue, 26 Oct 2021 10:22:34 +0100 [thread overview]
Message-ID: <e6140e0e73542662434046b163c02bca@hamnavoe.com> (raw)
In-Reply-To: <CAL6pNZ8JxE-2EcRD-CuOnhkZpM8W3NBPx9oV2CG_R5C_ygZv5w@mail.gmail.com>
> what you did was compile pprof (not shown...) great!, and then when you ran
> it,
> it failed... on the same machine?? but surely a cross plan 9, cross
> compiler/lnker/env
> is for getting plan 9 binaries going...
> or is your prompt modified??
I'll annotate the error message a bit for clarification:
> Building packages and commands for host, linux/amd64.
The failure occurred while building all of go for linux, on linux.
> # cmd/vendor/github.com/google/pprof/third_party/d3
This output line reports which package was being built when the failure occurred.
> unexpected fault address 0x607c60
> fatal error: fault
> [signal SIGBUS: bus error code=0x2 addr=0x607c60 pc=0x607c60]
There was a memory fault related to address 0x607c60 which is the same
as the program counter, suggesting the fault was a failure to fetch
the instruction at that address.
> goroutine 1 [running]:
> runtime.throw({0xce1702, 0xc00008d870})
> /sys/lib/go1.17/src/runtime/panic.go:1198 +0x71 fp=0xc00008d828
> sp=0xc00008d7f8 pc=0x435331
> runtime.sigpanic()
> /sys/lib/go1.17/src/runtime/signal_unix.go:732 +0x125
> fp=0xc00008d878 sp=0xc00008d828 pc=0x44b325
> cmd/compile/internal/typecheck.(*iexporter).pushDecl(0xc6e9c0,
> 0xc0000a2120)
> /sys/lib/go1.17/src/cmd/compile/internal/typecheck/iexport.go:403
> ...
> cmd/compile/internal/gc.Main(0xd16458)
> /sys/lib/go1.17/src/cmd/compile/internal/gc/main.go:307 +0x105b
> fp=0xc00008df20 sp=0xc00008dc98 pc=0xc0495b
> main.main()
> /sys/lib/go1.17/src/cmd/compile/main.go:55 +0xdd fp=0xc00008df80
The go runtime traceback suggests that the running binary is the go compiler,
which is being executed from the v9fs file system on the Plan 9 server.
The pc value 0x607c60 is within the text segment of the program, so I'm
guessing there was some problem fetching the page, which the linux kernel
reports as a "bus error" (a generic term for "something went wrong related
to memory").
There's plenty of disk space on the server.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tb065f4df67a8bab9-Mb6b34812de6756eda30d2665
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-10-26 9:22 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 11:03 [9fans] v9fs vs mmap Richard Miller
2021-10-24 19:50 ` [9fans] v9fs vs mmap (SOLVED) Richard Miller
2021-10-24 22:31 ` Conor Williams
2021-10-25 11:04 ` [9fans] v9fs vs mmap (not quite SOLVED) Richard Miller
2021-10-25 23:53 ` Conor Williams
2021-10-26 9:22 ` Richard Miller [this message]
2021-10-26 10:51 ` Richard Miller
2021-10-26 15:53 ` Dan Cross
2021-10-26 16:06 ` Conor Williams
2021-10-26 16:51 ` Richard Miller
2021-10-26 18:17 ` Skip Tavakkolian
2021-10-26 18:54 ` Conor Williams
2021-10-26 19:09 ` Richard Miller
2021-10-26 19:33 ` Skip Tavakkolian
2021-10-26 19:36 ` Skip Tavakkolian
2021-10-26 23:45 ` Skip Tavakkolian
2021-10-26 23:57 ` Charles Forsyth
2021-10-27 8:27 ` Richard Miller
2021-10-27 10:55 ` Richard Miller
2021-10-27 12:31 ` Dan Cross
2021-10-27 13:15 ` Richard Miller
2021-10-27 13:20 ` Dan Cross
2021-10-27 14:10 ` Richard Miller
2021-10-27 14:14 ` arnold
2021-10-27 14:39 ` Richard Miller
2021-10-27 14:45 ` arnold
2021-10-27 14:31 ` Dan Cross
2021-10-27 15:02 ` Bakul Shah
2021-10-27 15:37 ` Charles Forsyth
2021-10-27 16:34 ` Skip Tavakkolian
2021-10-27 18:37 ` Richard Miller
2021-10-27 19:12 ` Skip Tavakkolian
2021-10-27 19:30 ` [9fans] v9fs vs mmap (now SOLVED, we hope) Richard Miller
2021-10-27 20:18 ` Skip Tavakkolian
2021-11-03 14:44 ` Conor Williams
2021-11-03 16:39 ` Conor Williams
2021-11-01 2:58 ` [9fans] v9fs vs mmap (not quite SOLVED) Conor Williams
2021-11-04 0:32 ` Conor Williams
2021-11-04 3:15 ` Conor Williams
2021-11-04 11:49 ` Conor Williams
2021-11-05 3:16 ` Conor Williams
2021-11-05 10:21 ` Kenji Okamoto
2021-11-05 13:44 ` Conor Williams
2021-11-05 13:56 ` Conor Williams
2021-11-21 4:21 ` Conor Williams
2021-10-27 0:34 ` Conor Williams
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=e6140e0e73542662434046b163c02bca@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/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).