On Wed, Mar 22, 2006 at 04:04:03PM +0100, Lionel Elie Mamane wrote:
> tags 358362 +moreinfo
> 
> Thank you for your bug report.
> 
> What hardware (and drivers / firmware, if applicable) do you use?

> In particular, if you are using an Eicon (Diva) card, please try a
> newer version of capi4hylafax; newer version contain fixes
> specifically for Eicon/Diva cards. The version in Etch (Debian
> testing) should be fine.

The card is an AVM C4, because I saw the older, loger bugmail about
problems with c2faxrecv I updated the firmware to the newest available
version (from isdn4linux IIRC).
> 
> > /usr/sbin/capiinit status
> > 1 c4         running  c4-bc00          C4 3.11-06 0xbc00 21 0xff520000
> > 2 c4         running  c4-bc00          C4 3.11-06 0xbc00 21 0xff520000
> > 3 c4         running  c4-bc00          C4 3.11-06 0xbc00 21 0xff520000
> > 4 c4         running  c4-bc00          C4 3.11-06 0xbc00 21 0xff520000

I found not much, but the pattern from #4 to #3 where the address(?)
from Data gets shifted(?) into Params looks suspicious. I had no real
luck with the source. I had tried to build
capi4hylafax-01.03.00.99.svn.296 but then I would have to update to the
build dependencies: libcapi20-dev (>= 1:3.7.2005-07-09-2) libtiff4-dev (>= 
3.7.3).

I put in the questionmarks because I'm not sure what happens there. The
codelines gdb emitted on #3 looked different to what I expected but I
didn't check the preprocessed source.

If I should expect no problems with the newer version I would build and
rebuild affected packages,  but I have no urge to do that without your
comment on the expectation.

Thanks,
Peter

> On Wed, Mar 22, 2006 at 01:46:18PM +0100, Peter Wiersig wrote:
> 
> > Starting program: /usr/bin/c2faxsend -v -d 9761755 -f TIFF fritz_pic.tif
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 1082128752 (LWP 32149)]
> > 0x0000002a95eeef3c in memcpy () from /lib/libc.so.6
> > (gdb) bt
> > #0  0x0000002a95eeef3c in memcpy () from /lib/libc.so.6
> > #1  0x0000002a958d8062 in capi20_put_message () from /usr/lib/libcapi20.so.2
> > #2  0x000000000041afe0 in CapiBase_PutMessage (Base=0x542590, 
> > Message=0x5436800000 <Address 0x5436800000 out of bounds>) at
> CapiBase.h:74
> > #3  0x00000000004081e3 in CCAPI20_Channel::DataB3Req (this=0x407fe63e, 
> > Params=0x5436800000) at CapiMsg.h:353
> > #4  0x000000000040fd58 in CTransferChannel::PutData (this=0x7fbfff8160, 
> > Data=0x543680 "Sfff\001", DataLength=2048, hDataID=0x2)
> >     at Channel.cpp:353
> > #5  0x00000000004041e5 in CFaxSend::SendData (this=0x7fbfff8160) at 
> > faxsend.cpp:622
> > #6  0x0000000000411079 in CTransferChannel::ConnectB3ActiveInd 
> > (this=0x7fbfff8160, pNCPI=0x407ff3c0) at Channel.cpp:1094
> > #7  0x0000000000408de9 in CCAPI20_Channel::CONNECT_B3_ACTIVE_IND 
> > (this=0x7fbfff8160, NCCI=2048, pNCPI=0x407ff3c0) at
> CapiChan.cpp:655
> > #8  0x000000000040b4d3 in CCAPI20_MsgBase::HandleGetMessage 
> > (this=0x7fbfff8160, Message=0x54c8ae "\006") at osmem.h:116
> > #9  0x000000000041b106 in CapiBase_WaitForSignalThread (pice=0x542590) at 
> > CapiBase.cpp:164


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to