[Varnish] #1287: Varnish 3.0.3 - segfault in libvarnish.so.

[Varnish]

#1287: Varnish 3.0.3 - segfault in libvarnish.so.
------------------------------------+--------------------
 Reporter:  robroy                  |       Owner:
     Type:  defect                  |      Status:  new
 Priority:  normal                  |   Milestone:
Component:  varnishd                |     Version:  trunk
 Severity:  normal                  |  Resolution:
 Keywords:  segfault libvarnish.so  |
------------------------------------+--------------------

Comment (by coennie):

 Replying to [comment:4 martin]:

 Hi Martin,

 I've uploaded Archief.zip which contains the vcl and a core dump.

 Here's some technical extra information:

 {{{
 root at lb2:/proc/sys/kernel# /usr/sbin/varnishd -d -d -d -P
 /var/run/varnishd.pid -a :80 -T localhost:6082 -f /etc/varnish/default.vcl
 -S /etc/varnish/secret -s malloc,1536m
 Platform: Linux,2.6.32-5-xen-amd64,x86_64,-smalloc,-smalloc,-hcritbit
 200 246
 -----------------------------
 Varnish Cache CLI 1.0
 -----------------------------
 Linux,2.6.32-5-xen-amd64,x86_64,-smalloc,-smalloc,-hcritbit

 Type 'help' for command list.
 Type 'quit' to close CLI session.
 Type 'start' to launch worker process.

 start
 child (18281) Started
 200 0

 Child (18281) said Child starts
 Child (18281) died signal=11 (core dumped)
 Child cleanup complete
 child (18312) Started
 Child (18312) said Child starts
 }}}


 The segfault from coredump: [1204305.073356] varnishd[18300]: segfault at
 0 ip 00007fb19d296504 sp 00007fb18c5e3320 error 4 in
 libvarnish.so[7fb19d28a000+13000]

 This segfault has been create by: get /^J^J

 Hope to here from you soon as it's a big caching problem on our live
 enviroment now.

 The way I can get the varnished to create a segfault is by this command on
 a client:

 curl -X PURGE {any URL}

 Regards Coen

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1287#comment:5>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator