Opened 11 years ago
Closed 9 years ago
#5050 closed defect (wontfix)
When "gdal_ECW_JP2ECW" plugin is enabled exit code is always zero
| Reported by: | mise | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | default | Version: | unspecified |
| Severity: | normal | Keywords: | gdalwarp ECW gdal_ECW_JP2ECW plugin exit code zero |
| Cc: |
Description
The "gdal_ECW_JP2ECW" cause that application (gdalwarp ...) doesn't exit correctly.
Platform:
- Windows (tested on Windows 7 x64)
- x84 and x64
- Tested with GDAL: 1.8.1, 1.9.2, 1.10 (daily build)
Symptoms:
- Exit code is always zero
- Redirected STD streams buffers are not flushed (terminal is fine)
Add fflush() or disable stream buffer helped
Note:
- ECW SDK is not installed
Change History (3)
comment:1 by , 11 years ago
comment:2 by , 10 years ago
Perhaps this is causing an odd behaviour I have met with gdal_translate or ogr2ogr, I do not remember right now which one. Anyway, it was not possible to direct the messages from the screen into a file by adding ">command_log.txt" (I am on Windows as you can see) if the JP2ECW plugin file "gdal_ECW_JP2ECW.dll" was present in the plugin directory. Deleting it made forwarding to log file to work.
comment:3 by , 9 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Similar to #4830. Issue is somehow related to ECW SDK 3.x. Reopen if it appears with ECW SDK 5.x
Note:
See TracTickets
for help on using tickets.
I'm confused how you are using the ECW driver if the ECW SDK is not installed.
I have observed problems sometimes with the 3.3 SDK and things hanging on shutdown. Something about waiting for threads. I don't have a solution if that is what you are running into.