| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marko Tiikkaja <pgmail(at)joh(dot)to> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7516: PL/Perl crash |
| Date: | 2012-09-06 22:26:20 |
| Message-ID: | 19980.1346970380@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Marko Tiikkaja <pgmail(at)joh(dot)to> writes:
> On 03/09/2012 18:06, Tom Lane wrote:
>> This might be the wrong theory. You seem to have debug symbols for that
>> core dump --- can you tell which of the dereferences in line 3373
>> caused the crash?
> The current_call_data->prodesc->fn_readonly one.
> Please let me know if I can be of more assistance.
Hm, can you show us the contents of the *current_call_data struct?
Another thing that seems a bit risky is that plperl_func_handler sets up
current_call_data as a pointer to a mostly-zeroed struct and then does
assorted things that could throw error. That would leave a dangling
value of current_call_data ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-06 23:03:05 | Re: BUG #7516: PL/Perl crash |
| Previous Message | Alvaro Herrera | 2012-09-06 21:13:26 | Re: BUG #7521: Cannot disable WAL log while using pg_dump |