<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi Neels,
<div class=""><br class="">
</div>
<div class="">Issue is now in <a href="http://osmocom.org" class="">osmocom.org</a> issues list. Kindly see URL below:</div>
<div class=""><br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"></span><i class=""><u class=""><font color="#0433ff" class=""><a href="https://osmocom.org/issues/3182" class="">https://osmocom.org/issues/3182</a></font></u></i></div>
<div class=""><br class="">
</div>
<div class="">Thanks.<br class="">
<div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="Apple-interchange-newline">
Best Regard,</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
Ron Menez</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<a href="mailto:ron.menez@entropysolution.com" class="">ron.menez@entropysolution.com</a></div>
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Apr 17, 2018, at 4:48 PM, Ron <<a href="mailto:ron.menez@entropysolution.com" class="">ron.menez@entropysolution.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">Hi Neels,</div>
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class="">Thanks for your report!<br class="">
<br class="">
I can try to reproduce the issue, but if you have it available, the<br class="">
following would be immensely useful:<br class="">
<br class="">
You've offered the core file as download, but that is of no use without<br class="">
the exact matching binary. Please instead provide the backtrace like:<br class="">
<br class="">
gdb path/to/osmo-bsc core<br class="">
<blockquote type="cite" class="">bt<br class="">
</blockquote>
<br class="">
If the failure occurs reliably, you can also run osmo-bsc in gdb<br class="">
<br class="">
gdb --args osmo-bsc -c [...]<br class="">
<br class="">
When the segfault occurs, you'll get a gdb prompt and can do 'bt' to get a<br class="">
backtrace. If you are reproducing it, a network trace (pcap) of the events<br class="">
leading up to the failure would also be helpful.<br class="">
</blockquote>
<div class=""><br class="">
</div>
<div class="">We’ll be sharing the matching binary for this. We’ll try to replicate the segfault again and share the backtrace.</div>
<br class="">
<blockquote type="cite" class=""><br class="">
The default compilation should already include the debug symbols, i.e.<br class="">
CFLAGS containing "-g". Otherwise, the debian feeds also contain packages<br class="">
with debug symbols included.<br class="">
<br class="">
Ideally, you would create a new issue on <a href="http://osmocom.org/" class="">osmocom.org</a> in the OsmoBSC<br class="">
project and provide the backtrace, pcap and logs as attachments there.<br class="">
Attaching files to issues is preferable to sending mails with attachments,<br class="">
since everyone subscribed would receive attached files in their mail<br class="">
inboxes; we prefer to avoid that, for netiquette.<br class="">
</blockquote>
<div class=""><br class="">
</div>
<div class="">We already registered to <a href="http://osmocom.org/" class="">osmocom.org</a> and we’ll share the backtrace, logs, and pcap files to the issue register.</div>
<div class=""><br class="">
</div>
<div class="">Noted on sending mails with attachments. Apologies for our previous emails.</div>
</div>
<div class=""><br class="">
</div>
<div class="">
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
Best Regard,</div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
</div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
Ron Menez</div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<a href="mailto:ron.menez@entropysolution.com" class="">ron.menez@entropysolution.com</a></div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
</div>
</div>
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Apr 16, 2018, at 7:18 PM, Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" class="">nhofmeyr@sysmocom.de</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi Ron,<br class="">
<br class="">
Thanks for your report!<br class="">
<br class="">
I can try to reproduce the issue, but if you have it available, the<br class="">
following would be immensely useful:<br class="">
<br class="">
You've offered the core file as download, but that is of no use without<br class="">
the exact matching binary. Please instead provide the backtrace like:<br class="">
<br class="">
gdb path/to/osmo-bsc core<br class="">
<blockquote type="cite" class="">bt<br class="">
</blockquote>
<br class="">
If the failure occurs reliably, you can also run osmo-bsc in gdb<br class="">
<br class="">
gdb --args osmo-bsc -c [...]<br class="">
<br class="">
When the segfault occurs, you'll get a gdb prompt and can do 'bt' to get a<br class="">
backtrace. If you are reproducing it, a network trace (pcap) of the events<br class="">
leading up to the failure would also be helpful.<br class="">
<br class="">
The default compilation should already include the debug symbols, i.e.<br class="">
CFLAGS containing "-g". Otherwise, the debian feeds also contain packages<br class="">
with debug symbols included.<br class="">
<br class="">
Ideally, you would create a new issue on <a href="http://osmocom.org/" class="">osmocom.org</a> in the OsmoBSC<br class="">
project and provide the backtrace, pcap and logs as attachments there.<br class="">
Attaching files to issues is preferable to sending mails with attachments,<br class="">
since everyone subscribed would receive attached files in their mail<br class="">
inboxes; we prefer to avoid that, for netiquette.<br class="">
<br class="">
For creating issues, I will gladly provide permissions to your registered<br class="">
user. I see Justin Repello and Sonny Lafuente (sharing your email's domain<br class="">
name) registered at <a href="http://osmocom.org/" class="">osmocom.org</a>, and just gave those users "Developer"<br class="">
permissions. Let me know of any other users you would like me to enable.<br class="">
The enable step is merely to avoid spam, you're more than welcome to join<br class="">
anytime.<br class="">
<br class="">
Thanks!<br class="">
<br class="">
~N<br class="">
<br class="">
-- <br class="">
- Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" class="">nhofmeyr@sysmocom.de</a>> <a href="http://www.sysmocom.de/" class="">http://www.sysmocom.de/</a><br class="">
=======================================================================<br class="">
* sysmocom - systems for mobile communications GmbH<br class="">
* Alt-Moabit 93<br class="">
* 10559 Berlin, Germany<br class="">
* Sitz / Registered office: Berlin, HRB 134158 B<br class="">
* Geschäftsführer / Managing Directors: Harald Welte<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>