Anonymous | Login | Signup for a new account | 19-04-25 20:35 CEST | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||
ID | Project | Category | View Status | Date Submitted | Last Update | |
0001723 | SphereServer | executable - linux build | public | 20-02-10 19:50 | 16-03-10 10:20 | |
Reporter | HOCOK | |||||
Assigned To | ||||||
Priority | normal | Severity | crash | Reproducibility | random | |
Status | closed | Resolution | suspended | |||
Platform | OS | OS Version | ||||
Product Version | ||||||
Target Version | Fixed in Version | |||||
Summary | 0001723: Random crash | |||||
Description | Random crash without any info in logs. Can you suggest something to get crash information ? Maybe you can implement something in core and on crash it will display more info ? I think it's main thread crash, because it's looks like: while(1){print "Segmentation fault\n";} | |||||
Tags | No tags attached. | |||||
Nightly Version | Not Available | |||||
Experimental Flags | None | |||||
Option Flags | None | |||||
Internal Build Number | ||||||
Attached Files | ||||||
![]() |
||||||
|
![]() |
|
(0000409) MrSugarCube (administrator) 16-03-10 10:20 |
If there's any useful information it should already be printed on the console. I'm pretty sure this is related to 0001710, so I'll suspend this one. |
![]() |
|||
Date Modified | Username | Field | Change |
20-02-10 19:50 | HOCOK | New Issue | |
20-02-10 19:50 | HOCOK | Nightly Version | => Not Available |
20-02-10 19:50 | HOCOK | Experimental Flags | => None |
20-02-10 19:50 | HOCOK | Option Flags | => None |
16-03-10 10:19 | MrSugarCube | Relationship added | related to 0001710 |
16-03-10 10:20 | MrSugarCube | Status | new => closed |
16-03-10 10:20 | MrSugarCube | Note Added: 0000409 | |
16-03-10 10:20 | MrSugarCube | Resolution | open => suspended |
14-11-10 19:54 | MrSugarCube | Category | executable - linux => executable - linux build |
Copyright © 2000 - 2010 MantisBT Group |