Bug#320721: capi4hylafax: c2faxrecv segfaults when an incoming faxtransmission enters

2005-08-25 Thread Steve Langasek
Hi Hanno, On Thu, Aug 25, 2005 at 04:28:02PM +0200, Hanno 'Rince' Wagner wrote: > Better traceback: Thanks, this is the kind of backtrace that I was looking for. Unfortunately, it doesn't point me to a fix, because this: > #2 0x00412459 in CTransferChannel::DataB3Ind (this=0x539928, >

Bug#320721: capi4hylafax: c2faxrecv segfaults when an incoming faxtransmission enters

2005-08-25 Thread Hanno 'Rince' Wagner
Hi, Steve Langasek schrieb am 25. August 2005: > Well, it appears to have debugging symbols (i.e., line numbers) for the > capi4hylafax functions, but it doesn't actually look like it's related > to the c2faxrecv bug you were reporting... Better traceback: (gdb) run Starting program: /usr/bin/c

Bug#320721: capi4hylafax: c2faxrecv segfaults when an incoming faxtransmission enters

2005-08-25 Thread Steve Langasek
On Thu, Aug 25, 2005 at 08:17:19AM +0200, Hanno 'Rince' Wagner wrote: > Steve Langasek schrieb am 24. August 2005: > > > I fear I need the debug-Version of libc, not hylafax. > > Why? The backtrace you provided shows the segfault happens in hylafax code, > > not in glibc code. > Okay. I am not

Bug#320721: capi4hylafax: c2faxrecv segfaults when an incoming faxtransmission enters

2005-08-24 Thread Hanno 'Rince' Wagner
Hi, Steve Langasek schrieb am 24. August 2005: > > I fear I need the debug-Version of libc, not hylafax. > > Why? The backtrace you provided shows the segfault happens in hylafax code, > not in glibc code. Okay. I am not good in reading backtraces, but there are a lot of "empty" lines which I

Bug#320721: capi4hylafax: c2faxrecv segfaults when an incoming faxtransmission enters

2005-08-24 Thread Steve Langasek
On Thu, Aug 25, 2005 at 01:07:32AM +0200, Hanno 'Rince' Wagner wrote: > Steve Langasek schrieb am 23. August 2005: > > Could you try rebuilding capi4hylafax with debugging symbols as well > > (setting CXXFLAGS to "-g")? The backtrace you provided is missing the > > information that's needed to pi

Bug#320721: capi4hylafax: c2faxrecv segfaults when an incoming faxtransmission enters

2005-08-24 Thread Hanno 'Rince' Wagner
Hi Steve, Steve Langasek schrieb am 23. August 2005: > Could you try rebuilding capi4hylafax with debugging symbols as well > (setting CXXFLAGS to "-g")? The backtrace you provided is missing the > information that's needed to pinpoint the bug without being able to > reproduce it. I fear I need

Bug#320721: capi4hylafax: c2faxrecv segfaults when an incoming faxtransmission enters

2005-08-23 Thread Steve Langasek
Hi Hanno, Could you try rebuilding capi4hylafax with debugging symbols as well (setting CXXFLAGS to "-g")? The backtrace you provided is missing the information that's needed to pinpoint the bug without being able to reproduce it. If setting CXXFLAGS in the environment or in debian/rules doesn't

Bug#320721: capi4hylafax: c2faxrecv segfaults when an incoming faxtransmission enters

2005-07-31 Thread Hanno 'Rince' Wagner
Package: capi4hylafax Version: 1:01.02.03-10 Severity: grave Justification: renders package unusable c2faxrecv segfaults when a fax transmission comes in. I use a AVM B1 PCI V4.0-Card. Here are the interesting error messages: luggage:/var/log# dmesg|grep B1 b1pci: PCI BIOS reports AVM-B1 V4 at i/