[reSIProcate] Initialization
Hi ,
I am new to resiprocate stack, when i do make in the
resiprocate0.4.0/resiprocate directory, i get the following errors,
../build/../resiprocate/os/Data.hxx:220: error: an explicit specialization must
be preceded by 'template <>'
when i checked the code , it hits the following lines
namespace HASH_MAP_NAMESPACE
{
struct hash<resip::Data>
{
size_t operator()(const resip::Data& data) const;
};
}
I am not able to find out the problem, is there any configuration i am missing
out or any flags or something similar ?
Any help will be appreciated ...
Cheers,
Atmesh
-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Scott
Godin
Sent: Wednesday, April 20, 2005 5:42 AM
To: 'Sandeep Sharma'; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] Initialization seg fault
Sometime doing a complete rebuild - clears up these strange issues.
Note: I'm running the SVN head without any trouble. Do you get a seg fault
when running DUM\test\BasicCall too?
-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Sandeep
Sharma
Sent: Tuesday, April 19, 2005 6:17 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [reSIProcate] Initialization seg fault
I understand why it might be unstable currently and until the next
release.
Is there is a way to checkout the repository as it existed on March
25th? If yes, what is the command to do that?
I have had success with that version but do not have the source code
anymore. The latest versions are giving the seg fault.
Thanks
Sandeep
On Mon, 2005-04-18 at 10:58 -0700, Fischl jason wrote:
> We have had a very large amount of activity in the last few weeks so I
> would recommend updating frequently if you are going to sample the svn
> repository randomly. We do plan on releasing a stable tarball in the
> near future (weeks).
>
> Jason
>
>
> On 4/18/05, Sandeep Sharma <ssharma@xxxxxxxxxx> wrote:
> > Hello,
> >
> > I am getting a run-time (initialization) seg fault with the checkout
> > done late last week. I do not get this with the version checked out on
> > March 25th.
> >
> > Does anyone know what could be causing this? What is the recommended
> > practice for updating to the latest code base? I have been doing it
> > every 3-4 weeks.
> >
> > Thanks
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 16386 (LWP 16180)]
> > 0x40ac5e1b in resip::Data::rawCaseInsensitiveHash(char const*, unsigned)
> > () from ../lib/simplesd.so
> > (gdb) where
> > #0 0x40ac5e1b in resip::Data::rawCaseInsensitiveHash(char const*,
> > unsigned) () from ../lib/simplesd.so
> > #1 0x40ac5f5d in resip::Data::caseInsensitivehash() const ()
> > from ../lib/simplesd.so
> > #2 0x40ad588c in __gnu_cxx::hash<resip::Mime>::operator()(resip::Mime
> > const&) const () from ../lib/simplesd.so
> > #3 0x40af1961 in __gnu_cxx::hashtable<std::pair<resip::Mime const,
> > resip::ContentsFactoryBase*>, resip::Mime, __gnu_cxx::hash<resip::Mime>,
> > std::_Select1st<std::pair<resip::Mime const,
> > resip::ContentsFactoryBase*> >, std::equal_to<resip::Mime>,
> > std::allocator<resip::ContentsFactoryBase*>
> > >::_M_bkt_num_key(resip::Mime const&, unsigned) const ()
> > from ../lib/simplesd.so
> > #4 0x40af1852 in __gnu_cxx::hashtable<std::pair<resip::Mime const,
> > resip::ContentsFactoryBase*>, resip::Mime, __gnu_cxx::hash<resip::Mime>,
> > std::_Select1st<std::pair<resip::Mime const,
> > resip::ContentsFactoryBase*> >, std::equal_to<resip::Mime>,
> > std::allocator<resip::ContentsFactoryBase*>
> > >::_M_bkt_num_key(resip::Mime const&) const () from ../lib/simplesd.so
> > #5 0x40af1fda in __gnu_cxx::hashtable<std::pair<resip::Mime const,
> > resip::ContentsFactoryBase*>, resip::Mime, __gnu_cxx::hash<resip::Mime>,
> > std::_Select1st<std::pair<resip::Mime const,
> > resip::ContentsFactoryBase*> >, std::equal_to<resip::Mime>,
> > std::allocator<resip::ContentsFactoryBase*>
> > >::_M_bkt_num(std::pair<resip::Mime const, resip::ContentsFactoryBase*>
> > const&) const () from ../lib/simplesd.so
> > #6 0x40af1a81 in __gnu_cxx::hashtable<std::pair<resip::Mime const,
> > resip::ContentsFactoryBase*>, resip::Mime, __gnu_cxx::hash<resip::Mime>,
> > std::_Select1st<std::pair<resip::Mime const,
> > resip::ContentsFactoryBase*> >, std::equal_to<resip::Mime>,
> > std::allocator<resip::ContentsFactoryBase*>
> > >::find_or_insert(std::pair<resip::Mime const,
> > resip::ContentsFactoryBase*> const&) () from ../lib/simplesd.so
> > #7 0x40af1742 in __gnu_cxx::hash_map<resip::Mime,
> > resip::ContentsFactoryBase*, __gnu_cxx::hash<resip::Mime>,
> > std::equal_to<resip::Mime>, std::allocator<resip::ContentsFactoryBase*>
> > >::operator[](resip::Mime const&) () from ../lib/simplesd.so
> > #8 0x40bec92e in
> > resip::ContentsFactory<resip::PlainContents>::ContentsFactory() ()
> > from ../lib/simplesd.so
> > #9 0x40bec03f in resip::PlainContents::init() ()
> > from ../lib/simplesd.so
> > #10 0x40bec7d6 in __static_initialization_and_destruction_0(int, int) ()
> > from ../lib/simplesd.so
> > #11 0x40bec88a in _GLOBAL__I__ZN5resip13PlainContents5EmptyE ()
> > from ../lib/simplesd.so
> > #12 0x40c92a65 in __do_global_ctors_aux () from ../lib/simplesd.so
> > #13 0x40a8ac5d in _init () from ../lib/simplesd.so
> > --
> > Sandeep Sharma <ssharma@xxxxxxxxxx>
> >
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> >
--
Sandeep Sharma <ssharma@xxxxxxxxxx>
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an intended
recipient then please promptly delete this e-mail and any attachment and all
copies and inform the sender. Thank you.