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 327475 - __xmlRaiseError doesn't print line numbers from xmllint on Cygwin
__xmlRaiseError doesn't print line numbers from xmllint on Cygwin
Status: RESOLVED OBSOLETE
Product: libxml2
Classification: Platform
Component: xmllint
2.6.22
Other Cygwin
: Normal normal
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-18 03:14 UTC by Jonathan Lennox
Modified: 2017-06-14 11:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jonathan Lennox 2006-01-18 03:14:11 UTC
Please describe the problem:
Due (it seems) to DLL linking problems, on Cygwin, calls to __xmlRaiseError in
xmllint don't print the file and line numbers, instead printing only the message.

Steps to reproduce:
1. Install the Cygwin libxml2 package.
2. For the tests below, obtain and unpack the libxml2 source code.
3. xmllint -noout -schema libxml2-2.6.22/test/schemas/all_2.xsd
libxml2-2.6.22/test/schemas/all_2.xml 


Actual results:
Element 'c': This element is not expected.
libxml2-2.6.22/test/schemas/all_2.xml fails to validate

Expected results:
libxml2-2.6.22/test/schemas/all_2.xml:1: element c: Schemas validity error :
Element 'c': This element is not expected.
libxml2-2.6.22/test/schemas/all_2.xml fails to validate

Does this happen every time?
Yes.

Other information:
If xmllint is compiled statically, i.e. -static is passed to the libtool command
line when xmllint is compiled, the problem goes away.

The problem seems to occur because fprintf in a DLL has a different address than
fprintf in a main program, on Windows.
Comment 1 Nick Wellnhofer 2017-06-14 11:31:12 UTC
Closing 10 year old Cygwin issue as "obsolete".