Thanks. I'm still unable to get SQLite 3.15.0 to fail, in any way,
using your schema and data. Do you have any further hints on how I
can cause the problem to be expressed?
Is assertion fault reliably reproduced on your system?
On 11/1/16, mark wrote:
> On Tue Nov 01, 2016 at 09:21:04AM -0400,
On Tue Nov 01, 2016 at 03:15:43PM +, Simon Slavin wrote:
>
> On 1 Nov 2016, at 3:14pm, Rob Willett
> wrote:
>
> > We use the Perl DBD module all the time. What I would expect to see
> > is [... good stuff ...]
>
> Ah, thanks for the explanation. I always had trouble understanding
> Perl's
On 1 Nov 2016, at 3:14pm, Rob Willett wrote:
> We use the Perl DBD module all the time. What I would expect to see is [...
> good stuff ...]
Ah, thanks for the explanation. I always had trouble understanding Perl's
approach to anything. Hope the OP's problem gets solved.
Simon.
___
Simon,
We use the Perl DBD module all the time. What I would expect to see is
(IGNORE THE LINE BREAKS)
my $sth = $dbh->prepare("INSERT INTO
func_begin_change(
author,
author_contact,
author_contact_method,
author_shortname,
> On 1 Nov 2016, at 2:38pm, mark wrote:
>
>VALUES
>(
>?,
>?,
>?,
>?,
>?,
>?,
>?,
>?,
>?
>)
>;
>
> At least that is what I am passing to Perl's DBD::SQLite prepare(
On Tue Nov 01, 2016 at 09:21:04AM -0400, Richard Hipp wrote:
>
> The text of the SQL that is being prepared got cut off. Can you
> please send me the complete SQL statement that is being run at the
> point of the error?
INSERT INTO
func_begin_change(
author,
a
On 10/31/16, mark wrote:
> #18 0x17d970826118 in sqlite3RunParser (pParse=0x7f7e9200,
> zSql=0x17db9b16a600 "INSERT INTO\nfunc_begin_change(\n
> author,\nauthor_contact,\nauthor_contact_method,\n
> author_shortname,\nid,\nlang,\nmtime
On 10/31/16, mark wrote:
> #3 0x17d9707fb288 in valueFromExpr (db=0x17dbbac8e808,
> pExpr=0x17dc0252b288, enc=1 '\001', affinity=68 'D',
> ppVal=0x7f7e7f08,
> pCtx=0x7f7e7f70) at sqlite3.c:70020
> #4 0x17d9707fbaa0 in stat4ValueFromExpr (pParse=0x17db76d8f
On Tue Nov 01, 2016 at 02:21:02AM +0100, mark wrote:
> assertion "0" failed: file "sqlite3.c", line 70020, function
> "valueFromExpr"
I read the source code a little further and found that the NEVER at
line 70020 is actually a macro:
if( NEVER(op==TK_REGISTER) ) op = pExpr->op2;
Tha
On Mon Oct 31, 2016 at 05:42:32PM -0400, Richard Hipp wrote:
> On 10/31/16, mark wrote:
> > On Mon Oct 31, 2016 at 04:04:00PM -0400, Richard Hipp wrote:
> >> Is this reproducible?
> >
> > Yes... in that I can reliably get it to segfault. Duplicating the build
> > and/or statements leading up to th
On 10/31/16, mark wrote:
> On Mon Oct 31, 2016 at 04:04:00PM -0400, Richard Hipp wrote:
>> Is this reproducible?
>
> Yes... in that I can reliably get it to segfault. Duplicating the build
> and/or statements leading up to the fault outside of my environment
> is not so easy. Unless I make the vir
Is this reproducible?
Can you share with us the schema of the database file that was
connected when this error occurred?
On 10/31/16, mark wrote:
> Operating system: OpenBSD 6.0
> DBD::SQLite: 1.51_06
> sqlite:3.15.0
>
> Program received signal SIGSEGV, Segmentation fault.
> s
Operating system: OpenBSD 6.0
DBD::SQLite: 1.51_06
sqlite:3.15.0
Program received signal SIGSEGV, Segmentation fault.
sqlite3Step (p=0xb1480c37e08) at sqlite3.c:82102
82102 pCrsr = pC->uc.pCursor;
(gdb) list
82097
82098 assert( pOp->p1>=0 && pOp->p1nCursor );
82099
13 matches
Mail list logo
