[
https://issues.apache.org/jira/browse/SERF-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703259#comment-15703259
]
Michael Osipov edited comment on SERF-173 at 4/30/19 3:24 PM:
--------------------------------------------------------------
I am quite certain that Ivan's statement still holds true. You should provide
the core dump and see where the segfault happens (use GDB). I haven't had a
crash with Serf for years on four different operating systems.
was (Author: michael-o):
I am quite certain that Ivan's statement still holds true. You should provide
the core dumb and see where the segfault happens (use GDB). I haven't had a
crash with Serf for years on four different operating systems.
> 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)
