On May 29, 2010, at 10:19 AM, Albert Kim wrote:
Hi Dan,
It doesn't matter that it will never be written to. Since the
variable is a
non-const static it will get mapped into the WSD portion of memory.
Is a problem in practice? Or just messy?
Hi,
We are compiling sqlite 3.6.23.1 with the SQLITE_OMIT_WSD compile time flag
turned on. We are using the amalgamation. We found that this didn't
completely eliminate the writable static data in our binary, and some
investigation led me to this static variable:
SQLITE_PRIVATE VdbeOp
On May 28, 2010, at 1:11 AM, Kim, Albert wrote:
Hi,
We are compiling sqlite 3.6.23.1 with the SQLITE_OMIT_WSD compile
time flag turned on. We are using the amalgamation. We found that
this didn't completely eliminate the writable static data in our
binary, and some investigation
Hi Dan,
It doesn't matter that it will never be written to. Since the variable is a
non-const static it will get mapped into the WSD portion of memory.
There are actually a few other global static variables that are getting
placed in the WSD section of memory.
Here is a list of non-const
