After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 768511 - Random variable values from memory comes from exslt function with static return value
Random variable values from memory comes from exslt function with static retu...
Status: RESOLVED DUPLICATE of bug 602531
Product: libxslt
Classification: Platform
Component: general
1.1.29
Other Linux
: Normal normal
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2016-07-07 10:54 UTC by Alexius
Modified: 2016-07-07 16:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Test XSL (994 bytes, application/xslt+xml)
2016-07-07 10:54 UTC, Alexius
Details

Description Alexius 2016-07-07 10:54:42 UTC
Created attachment 330990 [details]
Test XSL

Hi @ll,

the attached XSL triggers random values from a global (static) variable comes as return value from an exslt function.

It seems to be a wrong memory read.

If I add more global variables after the "bugTrigger" variable, sometimes I see their values in "myResult" variable.

$ xsltproc ~/test.xsl ~/test.xsl
Comment 1 Nick Wellnhofer 2016-07-07 13:47:45 UTC
I can't reproduce this bug with libxslt 1.1.28 but it looks like a duplicate of bug #602531 which was recently fixed in the master branch. Can you build libxslt from Git and check whether this fixes your problem?

https://git.gnome.org/browse/libxslt/
Comment 2 Felix Hassert 2016-07-07 14:54:23 UTC
Thanks Nick, you are right! I can reproduce it with 1.1.28 and with 1.1.29 but not with current master (all built against libxml 2.9.4).

Your fix has just missed this year's "spring release". As the next release is probably almost half a year ahead, would you consider it safe for us to cherry pick your fix onto 1.1.29? It applies cleanly and make tests runs without errors.
Comment 3 Nick Wellnhofer 2016-07-07 16:04:06 UTC
I think the fix is safe but it's relatively invasive and I wanted to give it some testing. So I decided to integrate it early after the 1.1.29 release. If you find any issues, I will try to address them quickly.

*** This bug has been marked as a duplicate of bug 602531 ***