Original Message
Subject: Re: [sqlite] SQLite version 3.6.21
From: Andreas Schwab <sch...@linux-m68k.org>
To: sqlite-users@sqlite.org
Date: 2009-12-08 02:41
> $ ./sqlite3 :memory: 'create table test(integer)'
> Segmentation fault
We have the same problem and with
On Sun, Dec 13, 2009 at 10:53 PM, Roger Binns wrote:
> And just to blow your mind, SQLite supports zero length names too!
>
> create table ""("");
true, true
SQLite version 3.6.19
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> CREATE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Walter Dnes wrote:
> Possibly a stupid question from a relative newbie; shouldn't that be...
>
> sqlite3 :memory: 'create table test(fieldname integer)'
integer is not a reserved word so it is perfectly valid as a column name,
but I suspect the text
On 14 Dec 2009, at 4:38am, Walter Dnes wrote:
> On Tue, Dec 08, 2009 at 02:41:23AM +0100, Andreas Schwab wrote
>
>> It's still crashing due to undefined behaviour.
>>
>> $ ./sqlite3 :memory: 'create table test(integer)'
>> Segmentation fault
>
> Possibly a stupid question from a relative
On Tue, Dec 08, 2009 at 02:41:23AM +0100, Andreas Schwab wrote
> It's still crashing due to undefined behaviour.
>
> $ ./sqlite3 :memory: 'create table test(integer)'
> Segmentation fault
Possibly a stupid question from a relative newbie; shouldn't that be...
sqlite3 :memory: 'create table
D. Richard Hipp wrote:
> On Dec 8, 2009, at 9:51 AM, Andreas Schwab wrote:
>
>> "D. Richard Hipp" writes:
>>
>>> On Dec 7, 2009, at 8:41 PM, Andreas Schwab wrote:
>>>
D. Richard Hipp writes:
> As always, please let us know if you encounter any difficulties
>
>> And what compiler are you using that is sensitive to these violations
>> yet generates no warnings?
>
> It's the very nature of undefined behaviour that it does not require a
> warning. Welcome to the world of C.
Is the compiler you use a secret? Do you have to kill us if you tell the
"D. Richard Hipp" writes:
> For proof, could you please indicate where, exactly, we are violating C
> aliasing rules?
See the patch. You are storing a value of type void* in an object of
type Mem*. This is a classical example of an obvious aliasing
violation.
> And what
"D. Richard Hipp" writes:
> On Dec 7, 2009, at 8:41 PM, Andreas Schwab wrote:
>
>> D. Richard Hipp writes:
>>
>>> As always, please let us know if you encounter any difficulties with
>>> this or any other SQLite release.
>>
>> It's still crashing due to undefined behaviour.
>>
>>
On Dec 8, 2009, at 9:51 AM, Andreas Schwab wrote:
> "D. Richard Hipp" writes:
>
>> On Dec 7, 2009, at 8:41 PM, Andreas Schwab wrote:
>>
>>> D. Richard Hipp writes:
>>>
As always, please let us know if you encounter any difficulties
with
this or any other SQLite
On Dec 7, 2009, at 8:41 PM, Andreas Schwab wrote:
> D. Richard Hipp writes:
>
>> As always, please let us know if you encounter any difficulties with
>> this or any other SQLite release.
>
> It's still crashing due to undefined behaviour.
>
> $ ./sqlite3 :memory: 'create table test(integer)'
>
D. Richard Hipp writes:
> As always, please let us know if you encounter any difficulties with
> this or any other SQLite release.
It's still crashing due to undefined behaviour.
$ ./sqlite3 :memory: 'create table test(integer)'
Segmentation fault
Andreas.
--
Andreas Schwab,
SQLite version 3.6.21 is now available on the SQLite website:
http://www.sqlite.org/
SQLite version 3.6.21 is a monthly maintenance release of SQLite.
Upgrading from prior versions is optional. Version 3.6.21 features an
enhancement to the sqltie3_trace() interface such that the values of
13 matches
Mail list logo