From: | Dudás József <dudasj(at)piperh(dot)hu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: invalid memory alloc after insert with c trigger function |
Date: | 2007-06-01 11:00:30 |
Message-ID: | 465FFC4E.7000400@piperh.hu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
This is the debug of last varcharout routine:
Breakpoint 1, varcharout (fcinfo=0xbf8a1e7c) at varchar.c:441
441 VarChar *s = PG_GETARG_VARCHAR_P(0);
440 {
(gdb) print fcinfo
$25 = (FunctionCallInfo) 0xbf8a1e7c
441 VarChar *s = PG_GETARG_VARCHAR_P(0);
446 len = VARSIZE(s) - VARHDRSZ;
(gdb) print s
$28 = (VarChar *) 0xb5ebf024
447 result = palloc(len + 1);
(gdb) print len
$29 = -4
(gdb) next
Warning:
Cannot insert breakpoint -43.
Error accessing memory address 0xf72a1719: Input/Output error
> =?ISO-8859-2?Q?Dud=E1s_J=F3zsef?= <dj1999(at)freemail(dot)hu> writes:
>
>> I know that something doing wrong, but I can't find out what is it.
>>
>
> Getting a stack trace from the point of the errfinish call would
> probably help narrow it down. One thing that's not clear is whether
> SPI_modifytuple itself is failing (have you checked all the *other*
> arguments you're passing it?) or whether it happens later.
>
> regards, tom lane
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-06-01 11:07:59 | Re: invalid memory alloc after insert with c trigger function |
Previous Message | Anton | 2007-06-01 10:58:48 | Re: how to use array with "holes" ? |