Re: Segmentation fault with core dump

On 2013-04-10 16:53:12 -0500, Joshua Berry wrote:
> #7  0x0000000000638c78 in PortalRun (portal=0x2aa9360, count=10,
>     isTopLevel=1 '\001', dest=0x2a50c40, altdest=0x2a50c40,
>     completionTag=0x7fffd193d0f0 "") at pquery.c:787
>         save_exception_stack = 0x7fffd193cfe0
>         save_context_stack = 0x0
>         local_sigjmp_buf = {{__jmpbuf = {140736709513424,
> 8412518331319730861,
>               44733280, 0, 4294967295, 3, -8412469024494566739,
>               8412517527857939117}, __mask_was_saved = 0, __saved_mask = {
>               __val = {76, 44316880, 5, 0, 44804496, 767, 5, 0, 4294967295,
> 3,
>                 5565893, 11495616, 4746857, 140736709513424,
> 140736709513424,
>                 0}}}}
>         result = <value optimized out>
>         nprocessed = <value optimized out>
>         saveTopTransactionResourceOwner = 0x2a439e0
>         saveTopTransactionContext = 0x2a438d0
>         saveActivePortal = 0x0
>         saveResourceOwner = 0x2a439e0
>         savePortalContext = 0x0
>         saveMemoryContext = 0x2a438d0
>         __func__ = "PortalRun"

Ok, so while we have a valid resource owner up to here, portal->resonwer
is NULL.

Could you 'up' until youre in this frame and then do 'print *portal'?

Thanks,

Andres Freund

--
 Andres Freund                       http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services