Dueling symbols using PCRE emulation of POSIX ERE's

[Jeff Johnson]

When using yum+rpmlib, there appears to be confusions about which
"regcomp" symbol is to be used. Here's a trace from valgrind:

==1401==
==1401== Invalid write of size 1
==1401==    at 0x42A4770: regcomp (in /lib/libc-2.8.90.so)
==1401==    by 0x4AB97FB: mireRegcomp (mire.c:379)
==1401==    by 0x4A52FA7: rpmEVRmire (rpmevr.c:154)
==1401==    by 0x4A5300E: rpmEVRparse (rpmevr.c:164)
==1401==    by 0x49E10F6: rpmdsCompare (rpmds.c:3655)
==1401==    by 0x49E181D: rpmdsAnyMatchesDep (rpmds.c:3807)
==1401==    by 0x49B8BF0: rpmtsAddObsoletes (depends.c:481)
==1401==    by 0x49B984B: rpmtsAddInstallElement (depends.c:796)
==1401==    by 0x496F56A: rpmts_AddInstall (rpmts-py.c:440)


That forces MANDATORY INTERNAL PCRE always afaict.

I will proceed on that path. I can also change to using RPMMIRE_PCRE
always.

Other ideas?

73 de Jeff

==1401== by 0x40A0AF8: PyCFunction_Call (in /usr/lib/ libpython2.5.so.1.0) ==1401== by 0x40F0CEF: PyEval_EvalFrameEx (in /usr/lib/ libpython2.5.so.1.0) ==1401== by 0x40F2964: PyEval_EvalCodeEx (in /usr/lib/ libpython2.5.so.1.0) ==1401== Address 0x62b31c4 is not stack'd, malloc'd or (recently) free'd

smime.p7s
Description: S/MIME cryptographic signature