Re: [hylafax-users] faxq crashing with faxalter

[Chris Wong <wongc-hylafax@xxxxxxxx>]

On Thu, 23 Jun 2005, Chris Wong wrote:

> On Thu, 23 Jun 2005, Aidan Van Dyk wrote:
> 
> > * Chris Wong <wongc-hylafax@xxxxxxxx> [050623 14:36]:
> > > 
> > > I've checked out from CVS and I still see crashes in faxq. 
> > > 
> 
> > Can you get a gdb backtrace?
> > 

Here we go: 

Program received signal SIGSEGV, Segmentation fault.
DestInfo::isActive(Job&) const (this=0xd, job=@0x8069f18) at 
DestInfo.c++:69
69              for (Job* jp = running->dnext; jp != NULL; jp = jp->dnext)
(gdb) bt
#0  DestInfo::isActive(Job&) const (this=0xd, job=@0x8069f18)
    at DestInfo.c++:69
#1  0x0805a4e5 in faxQueueApp::runScheduler() (this=0x8068bf0)
    at faxQueueApp.c++:2190
#2  0x08053eaf in faxQueueApp::SchedTimeout::timerExpired(long, long) (
    this=0xd) at faxQueueApp.c++:72
#3  0xb7527c28 in TimerQueue::expire(timeval) () from 
/usr/lib/libfaxutil.so
#4  0xb7528fff in Dispatcher::notify(int, fd_set&, fd_set&, fd_set&) ()
   from /usr/lib/libfaxutil.so
#5  0xb7528afe in Dispatcher::dispatch(timeval*) ()
   from /usr/lib/libfaxutil.so
#6  0xb7528939 in Dispatcher::dispatch() () from /usr/lib/libfaxutil.so
#7  0x0805d053 in main (argc=2, argv=0xbfffb484) at faxQueueApp.c++:3257

To do this however, I had to use: -O2 -g -march=i386 -mcpu=i686 (mimicing 
the RPM build process, and making debugging very difficult). 

It sometimes takes a few tries with debug on. It's somewhat more
crash-prone after stripping the binary. I don't feel it's a compiler
optimizer bug since, when compiling with no optimization/arch, it will
generate a "Blocked by concurrent call" eventually.

Hope this helps,
Chris







____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*