false alarm (was: Re: ecasound gcc-3.3 exception problems)

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: false alarm (was: Re: ecasound gcc-3.3 exception problems)
From: Kai Vehmanen (k_AT_eca.cx)
Date: Fri May 30 2003 - 22:40:23 EEST

On Sat, 31 May 2003, Junichi Uekawa wrote:

>> ...? On my machine the above coredumps if ecasound was compiled with
>> gcc-3.3. :( It seems that there is something broken in C++ exception
> My ecasound binary doesn't coredump with your suggested command-line,

Ok, I investigated this issue a bit further and it turned out to be a
false alarm:

--cut--
###||$ ldd `which ecasound_debug` |grep stdc
        libstdc++.so.5 => /home/kaiv/apps/gcc-3.2/lib/libstdc++.so.5 (0x40150000)
[...]
###||$ ecasound_debug -i invalid
[...]
Aborted (core dumped)
--cut--

... but ...

--cut--
###||$ ldd `which ecasound_debug` |grep stdc
        libstdc++.so.5 => /home/kaiv/apps/gcc-3.3/lib/libstdc++.so.5 (0x40151000)
[...]
###| ~/pro-area |$ ecasound_debug -i invalid
ecasound: ERROR: [ECA-SESSION] : "(eca-chainsetup-parser) Input device or
file type invalid not recognized."
--cut--

So even if I compiled everything with the new 3.3, the ecasound binary was
dynamically linked against 3.2 libstdc++ and libgcc_s and resulted in core
dumps in exception handling. Updateing ld.so.conf helped to cure the
problem.

So I'll take back my earlier warning, ecasound compiled with gcc-3.3
_does_ work. :) 

-- 
 http://www.eca.cx
 Audio software for Linux!

New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Fri May 30 2003 - 22:41:13 EEST