Segmentation fault with RuleMatcher

[Yohann Thomas]

Here is the backtrace :

#0  0x080e1f6f in RuleMatcher::ExecRule ()
#1  0x080e1f22 in RuleMatcher::ExecRuleActions ()
#2  0x080e1be1 in RuleMatcher::Match ()
#3  0x080e1cb7 in RuleMatcher::FinishEndpoint ()
#4  0x0807082a in Connection::FinishEndpointMatcher ()
#5  0x080fc690 in TCP_Connection::Done ()
#6  0x080b7f29 in HTTP_Conn::Done ()
#7  0x080efda5 in NetSessions::Remove ()
#8  0x0806daf8 in Connection::DeleteTimer ()
#9  0x0806d3b3 in ConnectionTimer::Dispatch ()
#10 0x0810d651 in CQ_TimerMgr::DoAdvance ()
#11 0x0810d278 in TimerMgr::Advance ()
#12 0x080cc55e in dispatch_next_packet ()
#13 0x080cc9f1 in net_run ()
#14 0x0804e931 in main ()
#15 0x4022e7b8 in __libc_start_main () from /lib/tls/libc.so.6
#16 0xbffffe7a in ?? ()
#17 0x692d006f in ?? ()
Cannot access memory at address 0x72622f2e

Yohann.



Christian Kreibich wrote:

> Yohann,
>
> can you post the entire backtrace please? Thanks.
>
> Regards,
> Christian.
>
> On Tue, 2004-05-04 at 02:24, Yohann Thomas wrote:
> > But when I launch this on a real probe, I get a "Segmentation Fault"
> > after a random time.
> > I dumped a core, to locate the problem, and it seems to crash in
> > RuleMatcher::ExecRule.
>
> -- 
> ________________________________________________________________________
>                                           
> http://www.cl.cam.ac.uk/~cpk25 <http://www.cl.cam.ac.uk/%7Ecpk25>
>                                                     http://www.whoop.org
>
>