| Ticket Hash: | 78ee7b227909cf68b37a06b9988eec26a8bb3130 | ||
| Title: | crash - not sure if it was dashboard or -runtests or server. | ||
| Status: | Closed | Type: | Code_Defect |
| Severity: | Important | Priority: | Immediate |
| Subsystem: | Resolution: | Fixed | |
| Last Modified: |
2015-06-14 23:24:11 10.76 years ago |
Created: |
2014-10-16 22:25:27 11.42 years ago |
| Version Found In: | v1.6003 | ||
| User Comments: | ||||
|
matt added on 2014-10-16 22:25:27:
Error: (cadr) bad argument type: ()
Call history:
tasks.scm:67: sqlite3#make-busy-timeout
tasks.scm:71: sqlite3#set-busy-handler!
tasks.scm:72: conc
tasks.scm:72: sqlite3#execute
tasks.scm:75: file-read-access?
dashboard.scm:1457: sqlite3#finalize!
dashboard.scm:1508: get-environment-variable
dashboard.scm:1508: conc
dashboard.scm:1509: file-exists?
dashboard.scm:1513: args:get-arg
margs.scm:17: hash-table-ref/default
dashboard.scm:1524: args:get-arg
margs.scm:17: hash-table-ref/default
dashboard.scm:1525: args:get-arg
margs.scm:17: hash-table-ref/default
dashboard.scm:1525: string-split
matt added on 2015-06-14 23:24:11: Crash was due to calling dboard -test x,y where x or y was not an integer. Added check to catch. | ||||