|
From: Lorenzo M. <rai...@li...> - 2006-09-06 14:32:57
|
Hi,
I'm using Valgrind to check some custom modules I'm implementing in
Asterisk, a vast opensource PBX. I've been using it with no problem for
a long time, but a couple of days ago it started complaining giving me
this fatal error upon Asterisk boot:
--32215:0:aspacem Valgrind: FATAL: aspacem assertion failed:
--32215:0:aspacem aspacem_minAddr <= holeStart
--32215:0:aspacem at m_aspacemgr/aspacemgr.c:1997
(vgPlain_am_get_advisory)
--32215:0:aspacem Exiting now.
The problem was probably caused by the fact I've passed from the stable
branch of Asterisk to the SVN trunk, since it didn't happen before.
Digging through the old messages in the mailing list, I only could find
one related message of about a month ago, with the difference that in
that case the problem regarded holeEnd and not holeStart.
Could you help me understanding where the problem is, and how I could
try solving it?
I thank you in advance, best regards,
Lorenzo
--
http://confiance.sourceforge.net/
--
Il messaggio e' stato analizzato alla ricerca di virus o
contenuti pericolosi da MailScanner, ed e'
risultato non infetto.
|
|
From: Tom H. <to...@co...> - 2006-09-06 14:48:48
|
In message <44F...@li...>
Lorenzo Miniero <rai...@li...> wrote:
> I'm using Valgrind to check some custom modules I'm implementing in
> Asterisk, a vast opensource PBX. I've been using it with no problem for
> a long time, but a couple of days ago it started complaining giving me
> this fatal error upon Asterisk boot:
>
> --32215:0:aspacem Valgrind: FATAL: aspacem assertion failed:
> --32215:0:aspacem aspacem_minAddr <= holeStart
> --32215:0:aspacem at m_aspacemgr/aspacemgr.c:1997
> (vgPlain_am_get_advisory)
> --32215:0:aspacem Exiting now.
>
>
> The problem was probably caused by the fact I've passed from the stable
> branch of Asterisk to the SVN trunk, since it didn't happen before.
> Digging through the old messages in the mailing list, I only could find
> one related message of about a month ago, with the difference that in
> that case the problem regarded holeEnd and not holeStart.
It may well be the same problem though - try using the SVN build of
valgrind and see if that helps. You need at least revision 6001 to get
the fix for that problem.
> Could you help me understanding where the problem is, and how I could
> try solving it?
If there is still a problem it is in valgrind so you should open a
bug on the bug tracker.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Lorenzo M. <rai...@li...> - 2006-09-06 15:14:26
|
> > In message <44FEDC18.4080101 <at> libero.it> > Lorenzo Miniero <rainmaker <at> libero.it> wrote: > > > I'm using Valgrind to check some custom modules I'm implementing in > > Asterisk, a vast opensource PBX. I've been using it with no problem for > > a long time, but a couple of days ago it started complaining giving me > > this fatal error upon Asterisk boot: > > > > --32215:0:aspacem Valgrind: FATAL: aspacem assertion failed: > > --32215:0:aspacem aspacem_minAddr <= holeStart > > --32215:0:aspacem at m_aspacemgr/aspacemgr.c:1997 > > (vgPlain_am_get_advisory) > > --32215:0:aspacem Exiting now. > > > > > > The problem was probably caused by the fact I've passed from the stable > > branch of Asterisk to the SVN trunk, since it didn't happen before. > > Digging through the old messages in the mailing list, I only could find > > one related message of about a month ago, with the difference that in > > that case the problem regarded holeEnd and not holeStart. > > It may well be the same problem though - try using the SVN build of > valgrind and see if that helps. You need at least revision 6001 to get > the fix for that problem. > > > Could you help me understanding where the problem is, and how I could > > try solving it? > > If there is still a problem it is in valgrind so you should open a > bug on the bug tracker. > > Tom > Hi Tom, thanks a lot for the very quick answer. I just upgraded Valgrind to the SVN version (rev.6044), but the error is still there: the only difference is in the reported aspacemgr.c line, not 1997 anymore but 2003. I'll try on other machines too before opening a new bug in the tracker. In case the problem should appear on them too, I'll follow the guidelines on the site and report the bug to the tracker. Best regards, Lorenzo -- Il messaggio e' stato analizzato alla ricerca di virus o contenuti pericolosi da MailScanner, ed e' risultato non infetto. |