Documentation Source Text

Check-in [2b9db23f51]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix another typo in howtocorrupt.html
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 2b9db23f51cbc0431194aa36d659e9d996cc45a3
User & Date: drh 2016-07-22 15:42:06
Context
2016-07-23
14:58
Mention the sqlite3_expanded_sql() and sqlite3_trace_v2() interfaces in the change log. check-in: eecfde6ba8 user: drh tags: trunk
2016-07-22
15:42
Fix another typo in howtocorrupt.html check-in: 2b9db23f51 user: drh tags: trunk
2016-07-20
19:51
Fix typo in the how-to-corrupt document. check-in: d23e6d047a user: mistachkin tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/howtocorrupt.in.

363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
made.  Hence, recent versions of SQLite will subtly malfunction and may 
corrupt database files if used in multi-threaded application that run
on older linux systems that make use of LinuxThreads.</p>

<h3>6.2 Failures of mmap() on QNX</h3>

<p>There exists some subtle problem with mmap() on QNX such that making
a second mmap() call against the a single file descriptor can cause
the memory obtained from the first mmap() call to be zeroed.  SQLite on
unix uses mmap() to create a shared memory region for transaction 
coordination in [WAL | WAL mode], and it will call mmap() multiple times
for large transactions.  The QNX mmap() has been demonstrated to corrupt
database file under that scenario.  QNX engineers are aware of this problem
and are working on a solution; the problem may have already been fixed by
the time you read this.</p>







|







363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
made.  Hence, recent versions of SQLite will subtly malfunction and may 
corrupt database files if used in multi-threaded application that run
on older linux systems that make use of LinuxThreads.</p>

<h3>6.2 Failures of mmap() on QNX</h3>

<p>There exists some subtle problem with mmap() on QNX such that making
a second mmap() call against a single file descriptor can cause
the memory obtained from the first mmap() call to be zeroed.  SQLite on
unix uses mmap() to create a shared memory region for transaction 
coordination in [WAL | WAL mode], and it will call mmap() multiple times
for large transactions.  The QNX mmap() has been demonstrated to corrupt
database file under that scenario.  QNX engineers are aware of this problem
and are working on a solution; the problem may have already been fixed by
the time you read this.</p>