From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] werc memory over flow
Date: Fri, 11 Mar 2022 01:33:26 -0500 [thread overview]
Message-ID: <587431FA26E816F1525CE2A17493D0C9@eigenstate.org> (raw)
In-Reply-To: <E8B756286FD2FE6F8AE992EC2DA2E2DD@thinktankworkspaces.com>
Quoth william@thinktankworkspaces.com:
> I guess I'm really hammering away at this. I do have quite a bit of stuff, Some images,
> tables in html the rest is markdown.
>
> cat index.md | wc -l
> 128
>
> 128 lines is still low. Any thoughts? I can't go past this not even by one character
>
> memem user overflow
> pool sbrkmem block 4eed10
> hdr 0a110c09 00002020 0020cabc 00206fa7 3e703c0a 69206548
> tail 66647361 3e702f3c 3e703c0a 66647361 3e702f3c faf00000 | ef1300be 00002020
> user data 73 64 66 3c 2f 70 3e 00 | 00 f0 fa be 00 13 ef 20
> panic: pool panic
> sys: trap: fault read addr=0x0 pc=0x2150a6
> md2html.awk 9863: suicide: sys: trap: fault read addr=0x0 pc=0x2150a6
> Thu Mar 10 22:19:08 PST 2022 :: williamgunnells.com :: GET /pub/style/style.css HTTP/1.1 :: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 :: 200 :: http://williamgunnells.com/
Can you get a snap of the dead process, or at least a stack trace? (see snap(4))
next prev parent reply other threads:[~2022-03-11 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 6:24 william
2022-03-11 6:33 ` ori [this message]
2022-03-11 15:18 ` ori
2022-03-12 11:23 ` cinap_lenrek
2022-03-12 11:54 ` cinap_lenrek
2022-03-12 12:34 ` cinap_lenrek
2022-03-13 7:27 ` william
2022-03-13 21:16 ` cinap_lenrek
2022-03-12 13:27 ` Steve Simon
2022-03-12 14:38 ` Steffen Nurpmeso
2022-03-11 16:49 ` Nick Owens
2022-03-11 20:13 ` 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=587431FA26E816F1525CE2A17493D0C9@eigenstate.org \
--to=ori@eigenstate.org \
--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).