Skip site navigation (1) Skip section navigation (2)

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

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: use of initcap() causes segfault in v8.0.0beta5, where it doesn't in v7.4.6 (coredump included)
Date: 2004-11-27 02:20:00
Message-ID: 200411270320.00864.ftm.van.vugt@foxi.nl (view raw or flat)
Thread:
Lists: 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.


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2004-11-27 02:31:52
Subject: Re: use of initcap() causes segfault in v8.0.0beta5, where it doesn't in v7.4.6 (coredump included)
Previous:From: Tom LaneDate: 2004-11-27 01:17:16
Subject: Re: use of initcap() causes segfault in v8.0.0beta5, where it doesn't in v7.4.6 (coredump included)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group