Opened 15 years ago
Last modified 7 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 by , 15 years ago
| Milestone: | PostGIS 2.0.0 → PostGIS Future |
|---|
comment:2 by , 15 years ago
| Type: | defect → enhancement |
|---|
comment:3 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 12 years ago
I think its more so when a user sends an error its more helpful to us for debugging.
comment:6 by , 7 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
Note:
See TracTickets
for help on using tickets.
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.