Re: fmgr_info_cxt_security() screwing memory ?

Luis Vargas <Luis.Vargas@cl.cam.ac.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