_over_bluetooth(dp);
next_to_log_ptr = increase_ptr(next_to_log_ptr);
The details I haven't bothered with here is for example:
* don't log value that is ahead of next_insert_ptr
* cycle memory, when 8 gb is full, start again at 0 (or some address
above your code)
--
Fredrik Gustafsson
for
example) suit us better?
- Is a rebase workflow something we would benefit from?
All other questions, it seems like you're on top of already.
--
Fredrik Gustafsson
phone: +46 733-608274
e-mail: iv...@iveqy.com
website: http://www.iveqy.com
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Thank you very much for your help. Richard was correct in that it was a
memory error earlier.
/Fredrik
2016-02-04 16:53 GMT+01:00 Simon Slavin :
>
> On 3 Feb 2016, at 4:21pm, Fredrik Gustafsson wrote:
>
> > 223 rc = sqlite3_exec(db, "SELECT id, date, text FROM event
}
The callback function is never called.
Despite any errors in my code (which I'm sure there's), why does
sqlite3 crash this way?
--
Fredrik Gustafsson
phone: +46 733-608274
e-mail: iveqy at iveqy.com
website: http://www.iveqy.com
}
The callback function is never called.
Despite any errors in my code (which I'm sure there's), why does
sqlite3 crash this way?
--
Fredrik Gustafsson
phone: +46 733-608274
e-mail: iveqy at iveqy.com
website: http://www.iveqy.com
}
The callback function is never called.
Despite any errors in my code (which I'm sure there's), why does
sqlite3 crash this way?
--
Fredrik Gustafsson
phone: +46 733-608274
e-mail: iveqy at iveqy.com
website: http://www.iveqy.com
6 matches
Mail list logo