From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: line numbers in error messages are off wrt debuggers |
Date: | 2018-06-20 16:40:15 |
Message-ID: | 20180620164015.mfqhj754bgymcjiz@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2018-06-20 12:12:26 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > I'm fairly frequently annoyed that when I see an error message in the
> > log, I can't just generally set a breakpoint on the included line
> > number. That's because the line number in the error message is from the
> > *end* of the message:
>
> IME it varies depending on which compiler you use; some report the line
> where the ereport is. So I'm doubtful that there's going to be much we
> can do about it. Probably this behavior is bound up with macro expansion
> vs. just when __LINE__ is expanded.
Seems it can be hacked around: https://stackoverflow.com/a/13497879
But yikes, that's ugly.
There's apparenty some discussion in the standard committees trying to
unify the behaviour across compilers, but ...
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-06-20 16:42:59 | Re: Avoiding Tablespace path collision for primary and standby |
Previous Message | Bruce Momjian | 2018-06-20 16:38:57 | Re: Avoiding Tablespace path collision for primary and standby |