Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#22353 - [glib2] g_regex splitting on \s* gives no result

Attached to Project: Arch Linux
Opened by Tim (tes) - Friday, 07 January 2011, 20:38 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 02 February 2011, 15:01 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Ionut Biru (wonder)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Using g_regex_split_simple on a string with "\s*" as a pattern, there are no
results.
Reported upstream (https://bugzilla.gnome.org/show_bug.cgi?id=638894), but this seems to be Arch specific.

Steps to reproduce:
Run attached code, see that second regex has no output.
   test.c (0.3 KiB)
This task depends upon

Closed by  Ionut Biru (wonder)
Wednesday, 02 February 2011, 15:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  in future glib version. RIght now doesn't worth backporting or expect gnome to release a new stable glib including the fix
Comment by Ionut Biru (wonder) - Friday, 07 January 2011, 20:50 GMT
i mostly think is their fault because, if i remember well, they broke system pcre support on the road to 2.26.0.

can you try to rebuild your glib2 package removing the --with-pcre=system?
Comment by Tim (tes) - Friday, 07 January 2011, 22:13 GMT
Recompiling without system pcre indeed makes this behave correctly
Comment by Ionut Biru (wonder) - Wednesday, 02 February 2011, 14:53 GMT
i justed tested the development version of glib. is working fine with system pcre. I guess i can close this bug

Loading...