GNU C (Sourcery CodeBench 2011.03-95) version 4.5.2 (mips-linux-gnu)
compiled by GNU C version 4.3.2, GMP version 4.3.2, MPFR version
2.4.2, MPC version 0.8.1
On Mon, Mar 5, 2012 at 6:12 PM, Richard Hipp wrote:
> On Mon, Mar 5, 2012 at 7:04 AM, Sreekumar TP
On March 5, Richard Hipp wrote:
On Mon, Mar 5, 2012 at 1:39 PM, Larry Brasfield
wrote:
> On March 5, Richard Hipp wrote:
>
> On Mon, Mar 5, 2012 at 7:04 AM, Sreekumar TP
>> wrote:
>>
>> > The crash is a result of -O3 flag used during compiling the library.
>> >
>>
>> A compiler bug, then.
On Mon, Mar 5, 2012 at 1:39 PM, Larry Brasfield
wrote:
> On March 5, Richard Hipp wrote:
>
> On Mon, Mar 5, 2012 at 7:04 AM, Sreekumar TP
>> wrote:
>>
>> > The crash is a result of -O3 flag used during compiling the library.
>> >
>>
>> A compiler bug, then. OK. Good
On March 5, Richard Hipp wrote:
On Mon, Mar 5, 2012 at 7:04 AM, Sreekumar TP wrote:
> The crash is a result of -O3 flag used during compiling the library.
>
A compiler bug, then. OK. Good to know. SQLite has previously uncovered
bugs in GCC, MSVC, and LLVM. Which compiler are you using?
On Mon, Mar 5, 2012 at 7:04 AM, Sreekumar TP wrote:
> The crash is a result of -O3 flag used during compiling the library.
>
A compiler bug, then. OK. Good to know. SQLite has previously uncovered
bugs in GCC, MSVC, and LLVM. Which compiler are you using?
>
>
The crash is a result of -O3 flag used during compiling the library.
-Sreekumar
On Sat, Mar 3, 2012 at 2:00 PM, Sreekumar TP wrote:
> Its does not crash on x86. I havent built the shell for my mips device.
>
> Sreekumar
> On Mar 3, 2012 10:26 AM, "Dan Kennedy"
Its does not crash on x86. I havent built the shell for my mips device.
Sreekumar
On Mar 3, 2012 10:26 AM, "Dan Kennedy" wrote:
> On 03/03/2012 10:30 AM, Sreekumar TP wrote:
>
>> Could someone throw some light on this issue too?
>>
>
> I can't see from the stack trace why
On 03/03/2012 10:30 AM, Sreekumar TP wrote:
Could someone throw some light on this issue too?
I can't see from the stack trace why this is crashing.
Does it crash if you run the query from the sqlite shell?
Maybe try building the shell without optimizations, and
then running it under
Could someone throw some light on this issue too?
Sreekumar
On Mar 2, 2012 10:05 AM, "Sreekumar TP" wrote:
> The backtrace
> ===
>
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x2b657288 in sqlite3Parser (yyp=0x2d401e40, yymajor=119,
The backtrace
===
Program received signal SIGSEGV, Segmentation fault.
0x2b657288 in sqlite3Parser (yyp=0x2d401e40, yymajor=119, yyminor=...,
pParse=0x2d4035c8) at sqlite3.c:106740
106740 }while( yymajor!=YYNOCODE && yypParser->yyidx>=0 );
#0 0x2b657288 in sqlite3Parser
yes, will post the trace.
Sreekumar
On Mar 1, 2012 11:42 PM, "Dan Kennedy" wrote:
> On 03/01/2012 10:54 PM, Sreekumar TP wrote:
>
>> version 3.7.7.1
>> The query works on x86, but fails on MIPS processor!
>>
>
> Are you able to post a stack trace? Ideally generated by
>
On 03/01/2012 10:54 PM, Sreekumar TP wrote:
version 3.7.7.1
The query works on x86, but fails on MIPS processor!
Are you able to post a stack trace? Ideally generated by
the gdb "where full" command. Thanks.
Dan.
Sreekumar
On Thu, Mar 1, 2012 at 7:00 PM, Dan
version 3.7.7.1
The query works on x86, but fails on MIPS processor!
Sreekumar
On Thu, Mar 1, 2012 at 7:00 PM, Dan Kennedy wrote:
> On 03/01/2012 05:48 PM, Sreekumar TP wrote:
>
>> In my system, the statement causes sqlite3parser function to crash.
>> My compiler is
On 03/01/2012 05:48 PM, Sreekumar TP wrote:
In my system, the statement causes sqlite3parser function to crash.
My compiler is mips , little endian, gcc version is 4.5.2
SQLite version? 3.7.10 seems Ok here.
Dan.
___
sqlite-users mailing list
In my system, the statement causes sqlite3parser function to crash.
My compiler is mips , little endian, gcc version is 4.5.2
-Sreekumar
On Thu, Mar 1, 2012 at 2:59 PM, Simon Davies
wrote:
> On 1 March 2012 09:22, Sreekumar TP wrote:
>
On 1 March 2012 09:34, Petite Abeille wrote:
>
> On Mar 1, 2012, at 10:29 AM, Simon Davies wrote:
>
>>> doesnt work either.
>>>
>>
>> In what way does it fail to live up to your expectations?
>
> Simon? Are you impersonating Igor?!? :D
>
LOL :-)
On Mar 1, 2012, at 10:29 AM, Simon Davies wrote:
>> doesnt work either.
>>
>
> In what way does it fail to live up to your expectations?
Simon? Are you impersonating Igor?!? :D
___
sqlite-users mailing list
sqlite-users@sqlite.org
On 1 March 2012 09:22, Sreekumar TP wrote:
> doesnt work either.
>
In what way does it fail to live up to your expectations?
Regards,
Simon
___
sqlite-users mailing list
sqlite-users@sqlite.org
On Mar 1, 2012, at 10:22 AM, Sreekumar TP wrote:
> doesnt work either.
Sure it does.
sqlite> select count( distinct name ) from header;
899
___
sqlite-users mailing list
sqlite-users@sqlite.org
doesnt work either.
On Thu, Mar 1, 2012 at 2:50 PM, Petite Abeille wrote:
>
> On Mar 1, 2012, at 9:46 AM, Sreekumar TP wrote:
>
> > Is SELECT COUNT (DISTINCT column_name FROM table) syntax supported ?
>
> try:
>
> select count( distinct foo ) from bar
>
>
On Mar 1, 2012, at 9:46 AM, Sreekumar TP wrote:
> Is SELECT COUNT (DISTINCT column_name FROM table) syntax supported ?
try:
select count( distinct foo ) from bar
___
sqlite-users mailing list
sqlite-users@sqlite.org
Hi,
Is SELECT COUNT (DISTINCT column_name FROM table) syntax supported ?
The above causes a crash in sqlite3Parser function..
-Regards,
Sreekumar
___
sqlite-users mailing list
sqlite-users@sqlite.org
22 matches
Mail list logo