Change History (6)
comment:1 by , 22 years ago
| Owner: | changed from to |
|---|
comment:2 by , 22 years ago
comment:3 by , 22 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
I set the behavior in the current CVS release to cause a psAbort() in this scenario.
comment:4 by , 22 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
As we review the psError/psErrorMsg calls, I will review the use of psAbort and
exit. Should be completed by rel4.
In this particular case, an error, not abort, is probably appropriate.
comment:5 by , 22 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → new |
comment:6 by , 22 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Current behaviour is that psTraceSetLevel("") will generate an non-fatal error
and not exit to the OS. This seems reasonable.
-rdd
Note:
See TracTickets
for help on using tickets.

Please specify the correct behavior for
Should psAbort(), or log a warning?