MantisBT - Zandronum | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0002065 | Zandronum | [All Projects] Suggestion | public | 2015-01-15 16:03 | 2015-01-16 20:00 |
| Reporter | Edward-san | ||||
| Assigned To | |||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | Linux | OS | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Summary | 0002065: Add 'zandronum(-server)-dbg' package for debugging purpose | ||||
| Description | Now it's time to think about a way to make linux crash reports more reliable. The actual system makes this impossible, since zandronum is compiled in 'Release' mode. My idea for the zandronum-(server-)dbg package consists in: compile the code in RelWithDebInfo mode; separate the debug information in, for example, zandronum(-server).debug; strip the debug info in the original executable, ie zandronum(-server); link zandronum(-server).debug to zandronum(-server) as the debug info table. Then add such .debug files into the new packages. The instructions reported here show the whole idea better. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2015-01-15 16:03 | Edward-san | New Issue | |||
| 2015-01-15 16:04 | Edward-san | Summary | Add 'zandronum-debug' package for debugging purpose => Add 'zandronum(-server)-debug' package for debugging purpose | ||
| 2015-01-15 16:06 | Dusk | Note Added: 0011380 | |||
| 2015-01-15 17:05 | Edward-san | Summary | Add 'zandronum(-server)-debug' package for debugging purpose => Add 'zandronum(-server)-dbg' package for debugging purpose | ||
| 2015-01-15 17:05 | Edward-san | Description Updated | bug_revision_view_page.php?rev_id=6396#r6396 | ||
| Notes | |||||
|
|
|||||
|
|
||||