On 2018-06-20 12:12:26 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.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
