Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 443866 - dev-libs/xmlrpc-c-{1.28.03-r1,1.29.02}: segmentation fault in curlTransaction_destroy() when linked by net-misc/curl-7.26.0
Summary: dev-libs/xmlrpc-c-{1.28.03-r1,1.29.02}: segmentation fault in curlTransaction...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Andreis Vinogradovs ( slepnoga )
URL:
Whiteboard:
Keywords:
Depends on: 443872
Blocks:
  Show dependency tree
 
Reported: 2012-11-19 00:32 UTC by Oliver Freyermuth
Modified: 2013-01-01 18:32 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Freyermuth 2012-11-19 00:32:38 UTC 
After upgrading curl to current stable version 7.26 in tree, the client-component of xmlrpc-c segfaults on each request. 

gdb says: 
0x00007ffff7bd6514 in curlTransaction_destroy ()
   from /usr/lib64/libxmlrpc_client.so.3

This is easily reproducible when running the bundled xmlrpc-program (useflag: tools) with test-parameters (i.e. "xmlrpc 127.0.0.1 test"). 

Downgrading curl to 7.25.0-r1 fixes this. 

I think it is also fixed in a newer version of xmlrpc-c, but could not get it to build (yet). For example, the changelog of version 1.31 states: 
"Curl client XML transport: fix occasional crash with modern Curl introduced in 1.28."
Comment 1 Oliver Freyermuth 2012-11-19 00:58:50 UTC 
I have just successfully built the current "advanced" version of xmlrpc-c (1.32.04) and submitted a bump-request as #443872 with a slightly changed ebuild attached. 

I can now confirm that this bug is fixed in the new release when using it together with current curl 7.26.
Comment 2 Anthony Basile gentoo-dev 2012-12-23 13:22:24 UTC 
(In reply to comment #1)
> I have just successfully built the current "advanced" version of xmlrpc-c
> (1.32.04) and submitted a bump-request as #443872 with a slightly changed
> ebuild attached. 
> 
> I can now confirm that this bug is fixed in the new release when using it
> together with current curl 7.26.

This doesn't look like a curl bug.  I don't think I have anything to do here.  Am I reading this situation right?
Comment 3 Oliver Freyermuth 2012-12-23 22:21:13 UTC 
(In reply to comment #2)
> (In reply to comment #1)
> > I have just successfully built the current "advanced" version of xmlrpc-c
> > (1.32.04) and submitted a bump-request as #443872 with a slightly changed
> > ebuild attached. 
> > 
> > I can now confirm that this bug is fixed in the new release when using it
> > together with current curl 7.26.
> 
> This doesn't look like a curl bug.  I don't think I have anything to do
> here.  Am I reading this situation right?

Of course you are reading this right, I also believe this is clearly a bug in xmlrpc-c as it is fixed with their current upstream version. 

That's why I originally filed the bug with title 
"dev-libs/xmlrpc-c-1.28.03-r1 and -1.29.02 segfault with current net-misc/curl-7.26.0"
but apparently the title was mangled during bug-wrangling to something starting with "net-misc/curl" and then wrongly assigned. 

What is the correct procedure to re-assign this bug correctly to the xmlrpc-c maintainer, is there something I as the bug-reporter can / should do?
Comment 4 Anthony Basile gentoo-dev 2012-12-24 00:55:43 UTC 
The title and the fact it was assigned to me confused me.  I've corrected the report.
Comment 5 Andreis Vinogradovs ( slepnoga ) 2013-01-01 18:32:46 UTC 
Fixed in new version in tree
Comment 6 Andreis Vinogradovs ( slepnoga ) 2013-01-01 18:32:46 UTC 
Fixed in new version in tree