gvSIG bugs #3821
BusyBox crashes when gvSIG.sh is executed
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: | - | |||
| Category: | Application | |||
| Target version: | - | |||
| Severity: | Blocker | Add-on version: | ||
| gvSIG version: | 2.3.0 | Add-on build: | ||
| gvSIG build: | 2404 | Add-on resolve version: | ||
| Operative System: | Windows | Add-on resolve build: | ||
| Keywords: | Proyecto: | |||
| Has patch: | Hito: | |||
| Add-on name: | Unknown |
Description
Testing the gvSIG-desktop-2.3.0-2404-devel-win-x86_64-online.jar installer, I have found that BusyBox crashes when gvSIG.sh is executed. The reason seems to be explained in the CLI:
gvSIG.sh: trap: line 38: ERR: invalid signal specificationBut substituting ERR with e.g. SIGALRM, it crashes the same. Instead, commenting line 184:
#setPreferedArchitecturegvSIG.sh is executed without any apparent problems.
History
#1
Updated by Antonio Falciano over 8 years ago
- Status changed from New to Closed
BusyBox doesn't crash anymore in build 2405, so I close the ticket.