[Click] About element_error_hook

[Eddie Kohler]

Hi Roberto,

This is called due to a "%{element}" conversion in an errorhandler format 
string, for example:

errh->error("%{element}: problem", this);

You're getting a segfault because the thing passed in to the error() [or 
warning(), or message(), or whatever] function is not actually an element pointer.

Eddie


Roberto Riggio wrote:
> Hi,
> 
> a question for the core developer. I'm trying to track down a bug in my code and
> at some point I get a segmentation fault with the following details:
> 
> [Switching to Thread 0xb7c776c0 (LWP 26846)]
> 0x0819a483 in element_error_hook (val=0xbfe6c898) at ../lib/error.cc:743
> 743	    return e->declaration();
> 
> In which situation is element_error_hook called and by who (The method declaration is not
> overridden by my element).
> 
> R.
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click