Re: use of initcap() causes segfault in v8.0.0beta5, where it doesn't in v7.4.6 (coredump included) - Mailing list pgsql-bugs

From Frank van Vugt
Subject Re: use of initcap() causes segfault in v8.0.0beta5, where it doesn't in v7.4.6 (coredump included)
Date
Msg-id 200411270320.00864.ftm.van.vugt@foxi.nl
Whole thread Raw
In response to Re: use of initcap() causes segfault in v8.0.0beta5, where it doesn't in v7.4.6 (coredump included)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: use of initcap() causes segfault in v8.0.0beta5, where it doesn't in v7.4.6 (coredump included)
List pgsql-bugs
> Possibly a bug in your old glibc version?

Could be, a quick search does reveal some reports on a problem with the
combination of glibc 2.1.3 an towupper.

I'll look into the possibility of upgrading libc, but given the source of
oracle_compat.c, would it be possible to get the v7.4.6 behaviour back for
the time being by fiddling the #define USE_WIDE_UPPER_LOWER ? Or maybe by
using some specific configure option?


> BTW, would you confirm that that means

It does:

db=# show server_encoding;
 server_encoding
-----------------
 UNICODE
(1 row)

db=# show lc_ctype;
 lc_ctype
----------
 C
(1 row)



Hopefully some other Slackware / Debian user can confirm the segfault?





--
Best,




Frank.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: use of initcap() causes segfault in v8.0.0beta5, where it doesn't in v7.4.6 (coredump included)
Next
From: Tom Lane
Date:
Subject: Re: use of initcap() causes segfault in v8.0.0beta5, where it doesn't in v7.4.6 (coredump included)