Posted: Mon Jul 19, 2004 9:28 am Post subject: [Asterisk-bsd] No SIP on asterisk -c
If I start Asterisk with "-c" - console mode - Asterisk does not listen to the SIP socket at all.
If I start asterisk and then start a remote console (-r) everything works as expected...
Posted: Mon Jul 19, 2004 10:14 am Post subject: [Asterisk-bsd] No SIP on asterisk -c
On Mon, 2004-07-19 at 10:28, Olle E. Johansson wrote:
Quote:
If I start Asterisk with "-c" - console mode - Asterisk does not listen to the SIP socket at all.
If I start asterisk and then start a remote console (-r) everything works as expected...
This is on FreeBSD 4.9
Anyone else that recognizes this behaviour?
I saw this a week or so ago. But todays cvs head, with SO_NO_CHECK
removed :-), seems to be OK on 5.2.1.
Posted: Mon Jul 19, 2004 12:53 pm Post subject: [Asterisk-bsd] No SIP on asterisk -c
Yea, I recognize the symptom.
The editline library was causing memory corruption, and although I fixed one
instance of it, it sounds like there may be more. That's why invoking
asterisk without -c seems to help.
One way to attack this is to compile asterisk with gcc's bounds checking
extension. I'll take another look at that.
Rich
Quote:
-----Original Message-----
From: asterisk-bsd-admin@lists.digium.com
[mailto:asterisk-bsd-admin@lists.digium.com] On Behalf Of
Olle E. Johansson
Sent: Monday, July 19, 2004 4:29 AM
To: asterisk-bsd@lists.digium.com
Subject: [Asterisk-bsd] No SIP on asterisk -c
If I start Asterisk with "-c" - console mode - Asterisk does
not listen to the SIP socket at all.
If I start asterisk and then start a remote console (-r)
everything works as expected...
Posted: Mon Jul 19, 2004 1:00 pm Post subject: [Asterisk-bsd] No SIP on asterisk -c
Dr. Rich Murphey wrote:
Quote:
Yea, I recognize the symptom.
The editline library was causing memory corruption, and although I fixed one
instance of it, it sounds like there may be more. That's why invoking
asterisk without -c seems to help.
Also needs some attention, seems like a memory corruption, but on the
other hand the crash happens at the same spot all the time.
This happens in the dbput() app.
Posted: Mon Jul 19, 2004 1:26 pm Post subject: [Asterisk-bsd] No SIP on asterisk -c
Welcome sirs & madams!
Bug are stable, in pbx.c, e.g. in variaables substitutions. Still
findout and fixing.
We working third day incommand. Try to write extention, which will
recursively resolve more than 3 variables, you got coredump.
BR,
Oryx.
----- Original Message -----
From: "Olle E. Johansson" <oej@edvina.net>
To: <asterisk-bsd@lists.digium.com>
Sent: Monday, July 19, 2004 4:00 PM
Subject: Re: [Asterisk-bsd] No SIP on asterisk -c
Quote:
Dr. Rich Murphey wrote:
> Yea, I recognize the symptom.
>
> The editline library was causing memory corruption, and although I fixed
one
Quote:
> instance of it, it sounds like there may be more. That's why invoking
> asterisk without -c seems to help.
>
> One way to attack this is to compile asterisk with gcc's bounds checking
> extension. I'll take another look at that.
http://bugs.digium.com/bug_view_page.php?bug_id=0002067
Also needs some attention, seems like a memory corruption, but on the
other hand the crash happens at the same spot all the time.
This happens in the dbput() app.
Posted: Mon Jul 19, 2004 5:18 pm Post subject: [Asterisk-bsd] No SIP on asterisk -c
Quote:
-----Original Message-----
From: asterisk-bsd-admin@lists.digium.com
[mailto:asterisk-bsd-admin@lists.digium.com] On Behalf Of
Olle E. Johansson
Sent: Monday, July 19, 2004 8:01 AM
To: asterisk-bsd@lists.digium.com
Subject: Re: [Asterisk-bsd] No SIP on asterisk -c
Dr. Rich Murphey wrote:
> Yea, I recognize the symptom.
>
> The editline library was causing memory corruption, and although I
> fixed one instance of it, it sounds like there may be more. That's
> why invoking asterisk without -c seems to help.
>
> One way to attack this is to compile asterisk with gcc's bounds
> checking extension. I'll take another look at that.
http://bugs.digium.com/bug_view_page.php?bug_id=0002067
Also needs some attention, seems like a memory corruption,
but on the other hand the crash happens at the same spot all the time.
This happens in the dbput() app.
/O
Ah, wonderful! Anything reproducible will be *tremendously* easier to fix.
Feel free to mention them here or directly to me, 'cause I'd be glad to
help, and wouldn't have see it otherwise. In fact, feel free to assign any
reproducible FreeBSD bugs to me! [assuming that I'll get email then.]
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum