Mailing List Archive

#1822: Assert error in vwe_thread(), waiter/cache_waiter_epoll.c line 114
----------------------+-------------------
Reporter: lkarsten | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: varnishd | Version: trunk
Severity: normal | Keywords:
----------------------+-------------------
While playing around with GDB and setting thread names on Linux, I ran
into this:

{{{
varnish> panic.show
200
Panic at: Thu, 26 Nov 2015 14:32:58 GMT
"Assert error in vwe_thread(), waiter/cache_waiter_epoll.c line 114:
Condition(n >= 0) not true.
errno = 4 (Interrupted system call)
thread = (cache-epoll)
version = varnish-trunk revision 83aa540
ident =
Linux,3.16.0-4-amd64,x86_64,-junix,-smalloc,-smalloc,-hcritbit,epoll
Backtrace:
0x43c1a9: pan_backtrace+0x1d
0x43c5ae: pan_ic+0x2bc
0x47d82c: vwe_thread+0x3c4
0x7faf135200a4: libpthread.so.0(+0x80a4) [0x7faf135200a4]
0x7faf1325504d: libc.so.6(clone+0x6d) [0x7faf1325504d]

"
}}}

Being able to attach a debugger to a running Varnish is quite useful.

This may be as simple as handling EINTR return instead of asserting.

Coincidentally, the thread name work started with debugging a possible
waiter issue. Very nice symmetry.

--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1822>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs