Bogdan,
Yes I will enable those. This seems to be reproducing fairly often so hopefully
we will get some more info quickly. Is there anything else I need to collect at
time of the crash with this enabled or is the core dump sufficient?
Ben Newlin
From: Bogdan-Andrei Iancu
Date: Thursday,
Hi Ben,
This looks like very generic - a crash due a previous memory corruption
- is it possible for you to run with QM_MALLOC + DBG_MALLOC ? otherwise
it is rather impossible to identify the original source of corruption.
Thanks and regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and
Patch ec1889638a9d43280ba1362f6108a175efd4a854 (Proper error handling in
handle_subscribe) introduced a regression.
Now every time I receive a SUBSCRIBE (no matter what event: presence.winfo,
message-summary, xcap-diff, ...) I get this logged:
Jun 20 17:04:01 node15 ./opensips[26916]:
We have had another crash this morning: https://pastebin.com/dmXYbhzC
OpenSIPS version is the same as below.
Ben Newlin
From: Ben Newlin
Date: Wednesday, June 19, 2019 at 2:38 PM
To: OpenSIPS devel mailling list , Bogdan-Andrei
Iancu
Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash
The Github
Great News Bogdan and Team! What an amazing accomplishment! Looking forward
to seeing how OpenSIPs develops going forward from this milestone!
-Brett
On Wed, May 29, 2019 at 11:35 AM Bogdan-Andrei Iancu
wrote:
> Hi everyone !
>
> One and half month of testing, reporting, debugging, fixing and
The Github issue has the version info for that, for all the other crashes the
version is below.
$ opensips -V
version: opensips 2.4.5 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE
Branch: refs/heads/2.4
Home: https://github.com/OpenSIPS/opensips
Commit: aaa3fcf58c0523b57f2beb8c73edd0925b5a49bb
https://github.com/OpenSIPS/opensips/commit/aaa3fcf58c0523b57f2beb8c73edd0925b5a49bb
Author: Razvan Crainea
Date: 2019-06-20 (Thu, 20 Jun 2019)
Changed paths:
Branch: refs/heads/3.0
Home: https://github.com/OpenSIPS/opensips
Commit: 5d11bfbad163e9ba9bb2e8542538579da8e7575e
https://github.com/OpenSIPS/opensips/commit/5d11bfbad163e9ba9bb2e8542538579da8e7575e
Author: Razvan Crainea
Date: 2019-06-20 (Thu, 20 Jun 2019)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: b3e3eec97c108d357e2be5d58f5fc80edaa2dd90
https://github.com/OpenSIPS/opensips/commit/b3e3eec97c108d357e2be5d58f5fc80edaa2dd90
Author: Razvan Crainea
Date: 2019-06-20 (Thu, 20 Jun 2019)
Changed
Branch: refs/heads/2.4
Home: https://github.com/OpenSIPS/opensips
Commit: 87193522e463cb3f398c9618ec7a55edaf0bf180
https://github.com/OpenSIPS/opensips/commit/87193522e463cb3f398c9618ec7a55edaf0bf180
Author: Razvan Crainea
Date: 2019-06-20 (Thu, 20 Jun 2019)
Changed paths:
Branch: refs/heads/3.0
Home: https://github.com/OpenSIPS/opensips
Commit: 38c59a9071ddce91399bad2dd4882b29ab270cfa
https://github.com/OpenSIPS/opensips/commit/38c59a9071ddce91399bad2dd4882b29ab270cfa
Author: Razvan Crainea
Date: 2019-06-20 (Thu, 20 Jun 2019)
Changed paths:
I was wondering if it wouldn't make more sense to include minimalist modules
like the new uuid in the core package instead of splitting them into their own
package.
Right now there are 42 debian packages generated by opensips. This is a bit
excessive and it gets even worse with every new
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: efc8d6cc2a6057b86685911b725a22bd82766b92
https://github.com/OpenSIPS/opensips/commit/efc8d6cc2a6057b86685911b725a22bd82766b92
Author: Razvan Crainea
Date: 2019-06-20 (Thu, 20 Jun 2019)
Changed
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: ba623053eb1a9a8ee41a9f58680614083ba5b376
https://github.com/OpenSIPS/opensips/commit/ba623053eb1a9a8ee41a9f58680614083ba5b376
Author: Razvan Crainea
Date: 2019-06-20 (Thu, 20 Jun 2019)
Changed
14 matches
Mail list logo
