Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Varnish: Bugs

#1143: Slackware64-Current segfault

 

 

Varnish bugs RSS feed   Index | Next | Previous | View Threaded


varnish-bugs at varnish-cache

May 31, 2012, 10:46 AM

Post #1 of 3 (132 views)
Permalink
#1143: Slackware64-Current segfault

#1143: Slackware64-Current segfault
---------------------+------------------------------------------------------
Reporter: nanashi | Type: defect
Status: new | Priority: highest
Milestone: | Component: varnishd
Version: 3.0.2 | Severity: critical
Keywords: |
---------------------+------------------------------------------------------
I'm using slackware-current and although in slackware 32bit varnish
running normally. in my 64bit built I get a segmentation fault when
running varnish.


{{{
varnishd[3930]: Platform:
Linux,3.2.14-smp,x86_64,-sfile,-smalloc,-hcritbit
varnishd[3930]: child (3932) Started
kernel: [ 6274.568734] varnishd[3932]: segfault at 0 ip 0000000000414637
sp 00007fffb9d09d30 error 4 in varnishd[400000+79000]
varnishd[3930]: Child (3932) died signal=11
varnishd[3930]: Child (-1) said Child starts
}}}

regards

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

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


varnish-bugs at varnish-cache

May 31, 2012, 11:38 PM

Post #2 of 3 (123 views)
Permalink
Re: #1143: Slackware64-Current segfault [In reply to]

#1143: Slackware64-Current segfault
---------------------+------------------------------------------------------
Reporter: nanashi | Type: defect
Status: new | Priority: highest
Milestone: | Component: varnishd
Version: 3.0.2 | Severity: critical
Keywords: |
---------------------+------------------------------------------------------

Comment(by nanashi):

Rebuilt with --enable-debugging-symbols and it seems now that it's working
in x86_64.

Is it normal?

regards

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

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


varnish-bugs at varnish-cache

Jun 18, 2012, 3:26 AM

Post #3 of 3 (95 views)
Permalink
Re: #1143: Slackware64-Current segfault [In reply to]

#1143: Slackware64-Current segfault
-------------------------+--------------------------------------------------
Reporter: nanashi | Type: defect
Status: closed | Priority: highest
Milestone: | Component: varnishd
Version: 3.0.2 | Severity: critical
Resolution: worksforme | Keywords:
-------------------------+--------------------------------------------------
Changes (by tfheen):

* status: new => closed
* resolution: => worksforme


Comment:

No, this is not normal, but it's hard to tell what's going on without a
backtrace. I'm closing this bug for now. Please reopen if you can
reproduce this with a backtrace.

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

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

Varnish bugs RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.