Opened 11 years ago

Last modified 3 years ago

#317 new enhancement

Upgrade lwerror() to return file/linenumber information in error messages

Reported by: pramsey Owned by: pramsey
Priority: medium Milestone: PostGIS Fund Me
Component: postgis Version: master
Keywords: Cc:

Description

Right now LWDEBUGF() returns delightful contextual information, but the errors we show to our end users do not. That means (usually) the function names get manually embedded in the error strings for content. It would be nice to have that information by default, so error strings can spend their time being descriptive (or not).

Change History (6)

comment:1 Changed 11 years ago by pramsey

Milestone: PostGIS 2.0.0PostGIS Future

comment:2 Changed 11 years ago by pramsey

Type: defectenhancement

comment:3 Changed 8 years ago by nw

Owner: changed from mcayland to nw
Status: newassigned

Do we actually want to do this? The function/line numbers won't mean anything to an end user, though they would be nice to have in a bug report.

I think we'll have to change lwerror to a macro from a function. Presumably nothing is attempting to take the address of lwerror.

comment:4 Changed 8 years ago by robe

I think its more so when a user sends an error its more helpful to us for debugging.

comment:5 Changed 3 years ago by robe

Milestone: PostGIS FuturePostGIS Fund Me

Milestone renamed

comment:6 Changed 3 years ago by pramsey

Owner: changed from nw to pramsey
Status: assignednew
Note: See TracTickets for help on using tickets.