9front - general discussion about 9front
 help / color / mirror / Atom feed
* Re: [9front] acid:V: line in mkfile for pc64
       [not found] <4E3B69E98B663791E1EAB73ACDBDE6CA@hera.eonet.ne.jp>
@ 2021-01-29 13:41 ` cinap_lenrek
  2021-01-30  1:00   ` kokamoto
  0 siblings, 1 reply; 6+ messages in thread
From: cinap_lenrek @ 2021-01-29 13:41 UTC (permalink / raw)
  To: 9front

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [9front] acid:V: line in mkfile for pc64
  2021-01-29 13:41 ` [9front] acid:V: line in mkfile for pc64 cinap_lenrek
@ 2021-01-30  1:00   ` kokamoto
  2021-01-30  1:17     ` kokamoto
  0 siblings, 1 reply; 6+ messages in thread
From: kokamoto @ 2021-01-30  1:00 UTC (permalink / raw)
  To: 9front

[-- Attachment #1: Type: text/plain, Size: 137 bytes --]

Hi, thank you very much cinap.
I attached the crash screen, from which I took the
crash address for the analysis reported before.

Kenji

[-- Attachment #2: crash.jpg --]
[-- Type: image/jpeg, Size: 1549854 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [9front] acid:V: line in mkfile for pc64
  2021-01-30  1:00   ` kokamoto
@ 2021-01-30  1:17     ` kokamoto
  2021-02-08  4:35       ` kokamoto
  0 siblings, 1 reply; 6+ messages in thread
From: kokamoto @ 2021-01-30  1:17 UTC (permalink / raw)
  To: 9front

[-- Attachment #1: Type: text/plain, Size: 70 bytes --]

Sorry, I 'crashed' jpg file, and send again with gzipped file.

Kenji

[-- Attachment #2.1: Type: text/plain, Size: 320 bytes --]

from postmaster@ci5dell:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/x-gzip
	Content-Disposition: attachment; filename=crash.jpg.gz
	Content-Transfer-Encoding: base64

[-- Attachment #2.2: crash.jpg.gz.suspect --]
[-- Type: application/octet-stream, Size: 1549422 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [9front] acid:V: line in mkfile for pc64
  2021-01-30  1:17     ` kokamoto
@ 2021-02-08  4:35       ` kokamoto
  0 siblings, 0 replies; 6+ messages in thread
From: kokamoto @ 2021-02-08  4:35 UTC (permalink / raw)
  To: 9front

[-- Attachment #1: Type: text/plain, Size: 217 bytes --]


I resend three jpg images toke up at the booting 9pc64.
The first->last is the stream of it.

Those are the latest kernel made front the todya's 9front sources.

Kenji
PS: Above sourced kernel booted fine for 386 PC

[-- Attachment #2: DSC_0004.JPG --]
[-- Type: image/jpeg, Size: 655382 bytes --]

[-- Attachment #3: DSC_0005.JPG --]
[-- Type: image/jpeg, Size: 655503 bytes --]

[-- Attachment #4: DSC_0006.JPG --]
[-- Type: image/jpeg, Size: 238734 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [9front] acid:V: line in mkfile for pc64
  2021-01-27  0:12 kokamoto
@ 2021-01-28 12:57 ` cinap_lenrek
  0 siblings, 0 replies; 6+ messages in thread
From: cinap_lenrek @ 2021-01-28 12:57 UTC (permalink / raw)
  To: 9front

> How to use this line for debugging pc64 kernel?

i dont think this is used by anything.

kernel debugging can be done like:

acid -k -lkernel $pid <pathtokernel>

then type kinit(), and execute its output in the acid prompt,
which generates the needed acid files and includes.

i dont know why that acid rule was there in the mkfile.
sometimes i use acid files to quickly get the effective
size a struct for estimation of memory requirements.
maybe this was there as a shortcut for it?

--
cinap

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [9front] acid:V: line in mkfile for pc64
@ 2021-01-27  0:12 kokamoto
  2021-01-28 12:57 ` cinap_lenrek
  0 siblings, 1 reply; 6+ messages in thread
From: kokamoto @ 2021-01-27  0:12 UTC (permalink / raw)
  To: 9front

How to use this line for debugging pc64 kernel?

Kenji


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-02-08  4:50 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <4E3B69E98B663791E1EAB73ACDBDE6CA@hera.eonet.ne.jp>
2021-01-29 13:41 ` [9front] acid:V: line in mkfile for pc64 cinap_lenrek
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

9front - general discussion about 9front

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/9front

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 9front 9front/ http://inbox.vuxu.org/9front \
		9front@9front.org
	public-inbox-index 9front

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.9front


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git