| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Luis Vargas <Luis(dot)Vargas(at)cl(dot)cam(dot)ac(dot)uk> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: fmgr_info_cxt_security() screwing memory ? |
| Date: | 2007-10-12 22:07:29 |
| Message-ID: | 5806.1192226849@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Luis Vargas <Luis(dot)Vargas(at)cl(dot)cam(dot)ac(dot)uk> writes:
> Hi, I'm calling an arbitrary user-defined function from the backend.
> Although I can do it via FunctionCallInvoke, I have a weird problem when
> calling fmgr_info. The call results in a argument variable (eventType)
> being cleared. A gdb hardware watch says that the variable is modified by
> fmgr_info_cxt_security (fmgr.c:185): "finfo->fn_extra = NULL"; Any ideas of
> what is happening?
One wonders whether eventType points at already-pfreed memory. If not,
the problem must lie somewhere in the code you removed from the example.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-12 22:41:58 | Seems we need a post-beta1 initdb already |
| Previous Message | Luis Vargas | 2007-10-12 20:56:17 | fmgr_info_cxt_security() screwing memory ? |