https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092017-06-12T12:35:27ZOpen Source Mobile CommunicationsOsmoGSMTester - Bug #2321: osmo-gsm-tester: store properly coredump files when a process crasheshttps://projects.osmocom.org/issues/2321?journal_id=42612017-06-12T12:35:27Zpespin
<ul><li><strong>Subject</strong> changed from <i>osmo-gsm-tester: store properly coredump files whena process crash</i> to <i>osmo-gsm-tester: store properly coredump files when a process crashes</i></li></ul> OsmoGSMTester - Bug #2321: osmo-gsm-tester: store properly coredump files when a process crasheshttps://projects.osmocom.org/issues/2321?journal_id=42802017-06-13T22:55:18Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-1 priority-lowest closed" href="/issues/2325">Bug #2325</a>: sporadic shutdown of osmo-bts-trx in osmo-gsm-tester runs (no clock from trx)</i> added</li></ul> OsmoGSMTester - Bug #2321: osmo-gsm-tester: store properly coredump files when a process crasheshttps://projects.osmocom.org/issues/2321?journal_id=42812017-06-13T22:56:51Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>I remember to have seen a core file in a result tarball before, so I assumed this would work;<br />(except for the sysmobts, where we simply don't have code to copy a core file back to the workspace yet.)</p> OsmoGSMTester - Bug #2321: osmo-gsm-tester: store properly coredump files when a process crasheshttps://projects.osmocom.org/issues/2321?journal_id=42822017-06-14T00:41:51Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>The recent "crash" of osmo-bts-trx that made us question the working core dumps is actually an intentional shutdown by osmo-bts-trx (see <a class="issue tracker-1 status-3 priority-1 priority-lowest closed" title="Bug: sporadic shutdown of osmo-bts-trx in osmo-gsm-tester runs (no clock from trx) (Resolved)" href="https://projects.osmocom.org/issues/2325">#2325</a>) and is not expected to produce a core dump. Anyway, it can't hurt to verify that core dumps are working as intended.</p> OsmoGSMTester - Bug #2321: osmo-gsm-tester: store properly coredump files when a process crasheshttps://projects.osmocom.org/issues/2321?journal_id=42842017-06-14T00:41:58Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-1 status-3 priority-1 priority-lowest closed" href="/issues/2325">Bug #2325</a>: sporadic shutdown of osmo-bts-trx in osmo-gsm-tester runs (no clock from trx)</i>)</li></ul> OsmoGSMTester - Bug #2321: osmo-gsm-tester: store properly coredump files when a process crasheshttps://projects.osmocom.org/issues/2321?journal_id=52012017-08-28T10:17:59Zpespin
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>I verified that crash dumps are working correctly. I added some bits to osmo-gsm-tester manuals which were missing.</p>
<p>I had a brief look at automatically dumping the backtrace with gdb but doesn't seem to have high priority as anyway we have all binaries available in the tar.gz and can be easily debugged at any time.</p> OsmoGSMTester - Bug #2321: osmo-gsm-tester: store properly coredump files when a process crasheshttps://projects.osmocom.org/issues/2321?journal_id=57322017-10-11T02:54:37Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>