[Speex-dev] PocketPC 2005/echo canceller

[Aymeric Moizard]

I finally solved my problem:

My **static** speex library is compiled with:
-D_LIB

While I should compile it with:
-D_USRDLL

I'm not able to understand completely why: anyway, it
now can be compiled without breaking anything.

I'll now test wether the aec have an impact or not :)
tks,
Aymeric MOIZARD / ANTISIP
amsip - http://www.antisip.com
osip2 - http://www.osip.org
eXosip2 - http://savannah.nongnu.org/projects/exosip/


On Mon, 6 Nov 2006, Aymeric Moizard wrote:

>
>
> On Mon, 6 Nov 2006, Jean-Marc Valin wrote:
>
>> That's quite a strange problem. Considering that Speex doesn't have any
>> "init code" (stuff that executes when it's loaded), there's no way this
>> could be a bug in Speex.
>
> True.
>
>> I see two likely possibilities (plus lots of
>> unlikely):
>> 1) A bug in your code. Linking with Speex pushes your code to a
>> different place in memory and triggers the bug
>
> My next try will be to link with a minimal set of speex's file: that
> might help to see where the issue could be. (in case there is a relation
> with speex...)
>
>> 2) A bug in Visual Studio. You can just download the source code from
>> microsoft.com and track the bug down ;-)
>
> I have to give it a try ;/)
>
> tks!
> Aymeric
>
>> 	Jean-Marc
>> 
>> P.S. Actually, the only way it could be somewhat related to Speex is if
>> one of the symbols in Speex clashes with system functions, though I
>> think it's unlikely.
>> 
>> Aymeric Moizard a écrit :
>>> 
>>> Hi,
>>> 
>>> I'm experiencing weird problems while testing speex (I want to
>>> test the echo canceller first) on PDA with WM5 version pocket PC 2005.
>>> 
>>> Here is the strange scenario:
>>> 1-> App running without being linked with speex -> no problem
>>> 2-> App running while being linked with speex -> crash at always the same
>>>                                                  place.
>>>     NO ACCESS TO SPEEX IS DONE.
>>> 3-> I remove the speex dependancies/clean all object -> crash at always
>>>                                                         the same place
>>> 4-> reboot VisualStudio Application
>>> 5-> recompile everything without linking to speex: no crash....
>>> 
>>> I tried this several days: and retried those 5 steps several times. It's
>>> amazing but is really the way it is.
>>> 
>>> I suspect a bug in Visual Studio, of course... As It seems some have
>>> already tried WM5, I wish to ask if they met such issue and solved it?
>>> Just in case...
>>> 
>>> I also wish to test another application using speex to prove myself my
>>> application has a bug: if somebody has one, please send it.
>>> 
>>> Sorry for bothering you with probably non-speex problems,
>>> 
>>> Aymeric MOIZARD / ANTISIP
>>> amsip - http://www.antisip.com
>>> osip2 - http://www.osip.org
>>> eXosip2 - http://savannah.nongnu.org/projects/exosip/
>>> 
>>> _______________________________________________
>>> Speex-dev mailing list
>>> Speex-dev at xiph.org
>>> http://lists.xiph.org/mailman/listinfo/speex-dev
>>> 
>>> 
>> 
>