Re: M4 Problem with Macro 'regexp' (2)

[Stepan Kasal]

Dear Frank,
  thank you for your bug report and for your analysis.

I was able to reproduce your bug on two different GNU/Linux systems:
Fedora with glibc 2.3.3 and m4 1.4.1 and ROCK Linux with glibc 2.3.2
and m4 1.4.

I agree with you that the problem probably resides in the regex code
in GNU libc.

On Tue, Oct 12, 2004 at 01:58:58AM +0200, Frank Schwidom wrote:
> This is only read by me and not tested in any way, because i better keep 
> the present libc6 working on my computer. But, I hope, I could help 
> something.

Sure, it wouldn't be wise to manipulate your libc installation.
But you can easily compile regex code standalone.

Get reg*.* sources from the libc source and compile regex.c (it includes
the other *.c files).  Then you can link any program with it.
(Put a printf() call in, to make sure you really use your copy, not the
one from libc.)

You can then debug libc with your rebuilt m4, or with a small test
program (see the bug-regex*.c files in the libc source).

You should preferably work with the latest sources from CVS, see
http://sources.redhat.com/glibc/ for instruction.
(You can download individual files via the cvsweb interface, if you
connection is slow.)

As this is probably a bug in regex code in glibc, please report it to the
glibc people, preferably to http://sources.redhat.com/bugzilla/
(Of course, if you suceed to develop a small test case demonstrating the
bug, it would be great.)

This might be offtopic on this list, but I'd be glad if you kept me
informed by presonal mail (address@hidden).  You can also add my mail to the
cc list in bugzilla, if you report the bug.

Thank you very much for your work.  If you have resources to continue
with the debugging, thank you in advance for that.

Happy regexing,
        Stepan Kasal