Re: Printing backtrace of postgres processes - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Printing backtrace of postgres processes
Date
Msg-id 20210127170958.vzo33jzmqwhmn7z6@alap3.anarazel.de
Whole thread Raw
In response to Re: Printing backtrace of postgres processes  (vignesh C <vignesh21@gmail.com>)
Responses Re: Printing backtrace of postgres processes  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
Hi,

On 2021-01-27 19:05:16 +0530, vignesh C wrote:

>  /*
> + * LogBackTrace
> + *
> + * Get the backtrace and log the backtrace to log file.
> + */
> +void
> +LogBackTrace(void)
> +{
> +    int            save_errno = errno;
> +
> +    void       *buf[100];
> +    int            nframes;
> +    char      **strfrms;
> +    StringInfoData errtrace;
> +
> +    /* OK to process messages.  Reset the flag saying there are more to do. */
> +    PrintBacktracePending = false;

ISTM that it'd be better to do this in the caller, allowing this
function to be used outside of signal triggered backtraces.

>  
> +extern void LogBackTrace(void); /* Called from EmitProcSignalPrintCallStack */

I don't think this comment is correct anymore?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Improve join selectivity estimation using extended statistics
Next
From: Robert Haas
Date:
Subject: Re: cleaning up a few CLOG-related things