You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@serf.apache.org by "Branko Čibej (JIRA)" <ji...@apache.org> on 2019/04/30 15:44:00 UTC

[jira] [Commented] (SERF-173) serf_get crashes with segmentation fault on two requests and concurrent connections with SPNEGO auth

    [ https://issues.apache.org/jira/browse/SERF-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830419#comment-16830419 ] 

Branko Čibej commented on SERF-173:
-----------------------------------

Your stack trace is from {{svn checkout}}, not {{serf_get}} ... never mind. The pool allocator mutex is private to APR, you should at least check which version of APR you're using and probably upgrade to the latest version.

If this issue is still relevant, that is.

> serf_get crashes with segmentation fault on two requests and concurrent connections with SPNEGO auth
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SERF-173
>                 URL: https://issues.apache.org/jira/browse/SERF-173
>             Project: serf
>          Issue Type: Bug
>            Reporter: Michael Osipov
>            Priority: Major
>              Labels: Priority-Medium, Type-Defect
>
> Using FreeBSD 9.3-STABLE, Serf trunk@2500, MIT Kerberos 1.13.2.
> Calling {{./serf_get -d -c 2 -n 2 http://...}} gives me "Segmentation fault: 11 (Speicherabzug geschrieben)"
> Serf has been compiled with debug options, full logs, GDB stracktrace and core file can be send privately.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)