From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: can we quit patching quickjs?
Date: Tue, 16 Aug 2022 20:43:11 -0400 [thread overview]
Message-ID: <20220716204311.eklhad@comcast.net> (raw)
In-Reply-To: <Yvw2ND/DUWLnIKT2@codewreck.org>
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
Perhaps your build is 64-bit machine, with 8-byte pointers instead of 4-byte pointers.
I can't see any other way that location would push out so far.
I could change the range to 400.
I don't want to make it too high or I could be trolling on invalid memory.
Remember, I don't know the size of the struct.
It is opaque in every way.
I'm not counting on a debug symbol to do this, just the global variables that have to be there for anyone to link against the quick library.
Karl Dahlke
prev parent reply other threads:[~2022-08-17 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 23:40 Karl Dahlke
2022-08-17 0:28 ` Dominique Martinet
2022-08-17 0:43 ` Karl Dahlke [this message]
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=20220716204311.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.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).