From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] werc memory over flow
Date: Sun, 13 Mar 2022 00:27:44 -0700 [thread overview]
Message-ID: <51F83C65A544C3F1BA5C463D766F927F@thinktankworkspaces.com> (raw)
In-Reply-To: <E1ED69C19FDE2025CC3051F1DDD7E6C7@felloff.net>
Sorry I got caught up doing other stuff. I did try acid but had a permission
error which is probably expected or maybe it was a read error I can't remember.
But acid wasn't printing lst() or anything else.
The wrapper would have been the best step. However I did another pull and
merged your branch and 'mk install' The fix seems to work great.
On a side not how do I make a push not that I have anything to push considering
i'm new to this. Do I need to fork a branch and submit a pr or what.
I suspect I need an account or I can create another branch and just paste a diff
into an email. NOT that I have anything to contribute at this point. Just curious.
Regards,
-Will
Quoth cinap_lenrek@felloff.net:
> arg, also have to not do this:
>
> - *pb = '\0';
> setsval(x, buf); /* BUG: should be able to avoid copy + free */
>
> was already been done by the copy loop before:
>
> while ((*pb++ = *sptr++) != 0)
> ;
>
> i commited the fix now.
>
> please report if that fixes the issue.
>
> --
> cinap
>
next prev parent reply other threads:[~2022-03-13 8:01 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
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 [this message]
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=51F83C65A544C3F1BA5C463D766F927F@thinktankworkspaces.com \
--to=william@thinktankworkspaces.com \
--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).