RE: xsltproc segfaults after upgrading to docbook xsl stylesheets v1.60.1

[günter strubinsky]

That's the beauty of open software, Patrick. The source is available. If
it's not good enough for you, you can just 'make it happen'. As you found
out, there are other packages too that you could use to replace those not to
your liking. Most of the people working on those packages do it voluntarily
and do not appreciate 
-   being bitched at
-   are suggested -between the lines- to being fired

Long time ago, very long time ago, I played in the open software field too,
for the simple reason that I wanted to do something that I really cared for;
like -as I assume- many do nowadays. I ceased working in this area because
of people like you.

If you have the qualification, fix it. If you don't, than we can safely
assume that you don't know about the problems and side effects that need to
be solved and also that you have no idea of how long it will take to work
perfect. Those individuals you are griping about are not your slaves but do
valuable work for all of us on their free will and their own time and
deserve your appreciation instead of being publicly attacked.

Very frustrated

 günter strubinsky
 [EMAIL PROTECTED]
 Tel: 402.212.0196

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
 Of Patrick Eisenacher
 Sent: Monday, March 24, 2003 6:15 AM
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: Re: xsltproc segfaults after upgrading to docbook xsl stylesheets
 v1.60.1
 
 Hi Jeff,
 
 I'm waiting already for more than a month for this to happen. Needless
 to say, I'm pretty frustrated. But despite Robert claiming to take care
 of this in his initial response you cited below, no update was ever
 published. All further inquiries were silently ignored. The
 interpretation of this behaviour and consequences are up to you.
 
 Right now, Cygwin is not usable for XML editing. I recommend switching
 over to some other *nix and a VM. Alternatively you can use the Windows
 ports of the xml libaries provided by Igor Zlatkovic. His ports are
 always up to date: http://www.zlatkovic.com/projects/libxml/index.html
 
 
 Disappointed,
 Patrick
 
  Robert Collins said on 19 Feb 2003 07:57:58 +1100:
  Yes, and this takes the current version from 'old' to 'old + buggy'.
  I've upped my priority to get a new release out. Uhmm, end of the week
  should do it.
 
  Please, could we/you somehow get xsltproc  associated libs in the
 cygwin
  installation repository brought up-to-date? I'm trying to use xsltproc
 with
  some docbook stuff (we're using docbook to write the next phase of
  ProjectLiberty specs, and I use cygwin as my *nix environment), and said
  docbook stuff uses xinclude. The old xsltproc et al included (still) in
 the
  cygwin install (I updated this morning) barfs on the xinclude stuff,
 plus it
  doesn't properly handle (eg skip over) included mediaobjects (eg EPS).
 The
  latest version of xsltproc et al (the various *xml* libs) handles both
 of
  these just fine.
 
  thanks,
 
  JeffH
 
 
 
 --
 Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
 Bug reporting: http://cygwin.com/bugs.html
 Documentation: http://cygwin.com/docs.html
 FAQ:   http://cygwin.com/faq/



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

xsltproc segfaults after upgrading to docbook xsl stylesheets v1.60.1

[Patrick Eisenacher]

Greetings,

I just posted the attached mail to the docbook-apps list. Daniel 
Veillard pointed out that libxml and libxslt are quite old and that this 
bug has been fixed since then.

Indeed, verifying this with the Windows binaries provided by Igor 
Zlatkovic at http://www.zlatkovic.com/projects/libxml/ proved that the 
segfault went away and my document gets smoothly transformed again.

E:\Temp\libxslt-1.0.26.win32\utilxsltproc -version
Using libxml 20503, libxslt 10026 and libexslt 717
xsltproc was compiled against libxml 20503, libxslt 10026 and libexslt 717
libxslt 10026 was compiled against libxml 20503
libexslt 717 was compiled against libxml 20503

May I ask the libxml and libxslt package maintainer to upgrade the 
packages to a newer version that fixes the crash. Are you still the 
maintainer, Robert?


Thanks for your help,
Patrick
---BeginMessage---
Greetings,

I just upgraded my XSL stylesheets from 1.50.1 to 1.60.1 and now 
xsltproc complains about an undefined namespace and segfaults on one of 
my documents. The culprit seems to be a fileref, on which xsltproc chokes.

Is this a stylesheet issue or an xsltproc issue? Can anybody help?


Thanks,
Patrick


$ xsltproc -version
Using libxml 20423, libxslt 10013 and libexslt 705
xsltproc was compiled against libxml 20417, libxslt 10013 and libexslt 705
libxslt 10013 was compiled against libxml 20417
libexslt 705 was compiled against libxml 20417


$ xsltproc -catalogs -o Specification.html 
/usr/local/lib/xml/stylesheets/docbook-xsl/html/docbook.xsl 
Specification.xml
Error Undefined namespace prefix
xmlXPathCompiledEval: evaluation failed
Segmentation fault (core dumped)


here's a doc to reproducce the segfault:
?xml version=1.0 standalone='no'?
!DOCTYPE article PUBLIC -//OASIS//DTD DocBook XML V4.2//EN
  http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd;

!-- ROOT ELEMENT --
article class=specification lang=en vendor=Fillmore Labs 
revision=0.4

section id=architecture
titleArchitecture/title
figure id=architecture-system
titleSystem Architecture/title
mediaobject
imageobject
imagedata 
fileref=Specification/ArchitectureSystem.jpg format=JPG 
align=center /
/imageobject
textobject
phraseSystem Architecture/phrase
/textobject
/mediaobject
/figure
/section
/article


Exception: STATUS_ACCESS_VIOLATION at eip=6103E17D
eax=004B ebx=0001 ecx=FFF9 edx=610C4F84 esi=0001 
edi=10D83838
ebp=0022F000 esp=0022EFE8 program=D:\Cygwin\bin\xsltproc.exe
cs=001B ds=0023 es=0023 fs=0038 gs= ss=0023
Stack trace:
Frame Function  Args
0022F000  6103E17D  (10D83AC0, 103A62A0, 10A2DAB0, )
0022F030  6103EC46  (0001, 103A6B20, 10A2E160, 10D83838)
0022F060  0041A67D  (10D9A008, 0042BAA0, 103A6018, 6107A320)
0022F090  0041A6DB  (10D99F88, 10A2DAB0, 0022F100, 004291B2)
0022F100  0042968D  (10A2DAB0, 10A2E160, 103A6B20, )
0022F160  0041AB1A  (10A2DAB0, 10D839F0, 103A5EA8, 10D83870)
0022F190  0041B797  (10A2DAB0, 103A5EA8, 103A6B20, 10D83838)
0022F1C0  0041B86E  (10A2DAB0, 103A5EA8, 103A6B20, )
0022F200  0041BE2F  (10A2DAB0, 103A6838, , 103CCB70)
0022F260  0042922D  (10A2DAB0, 10A2E160, 103A68F0, 10392140)
0022F2A0  00428B44  (10A2DAB0, 10A2E160, , 6103EC46)
0022F330  0042C504  (10A2DAB0, 10A2DEE8, 10486818, 104850B8)
0022F390  004291B2  (10A2DAB0, 10A2DEE8, 104866F8, )
0022F3F0  0042C823  (10A2DAB0, 10A2DEE8, 10484538, 10484C58)
0022F450  004291B2  (10A2DAB0, 10A2DEE8, 10483BD8, 10490E48)
0022F4A0  0042BC41  (10A2DAB0, 10A2DEE8, 1048BC90, 1048B760)
End of stack trace (more stack frames may be present)


---End Message---
--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/