Re: [HACKERS] \x output blowing up

2005-09-25 Thread Martijn van Oosterhout
On Sat, Sep 24, 2005 at 07:18:16PM -0400, Bruce Momjian wrote: > > Well, it seems we are going to have to fix it somehow for 8.1. It is > not crashing here so I can't work up a patch. Can you submit a minimal > fix for 8.1? Thanks. Ah, it would only happen if your encoding was UTF-8 since that

Re: [HACKERS] \x output blowing up

2005-09-24 Thread Bruce Momjian
Well, it seems we are going to have to fix it somehow for 8.1. It is not crashing here so I can't work up a patch. Can you submit a minimal fix for 8.1? Thanks. --- Martijn van Oosterhout wrote: -- Start of PGP signed sec

Re: [HACKERS] \x output blowing up

2005-09-24 Thread Martijn van Oosterhout
On Sat, Sep 24, 2005 at 11:45:08PM +0200, Martijn van Oosterhout wrote: > Hi, > > On CVS tip, whenever I do \x output, it dies with an internal error in > glibc on free. If you run it under valgrind, it complains about these > lines of code: Ok, I worked out the direct cause, pg_wcswidth only r

[HACKERS] \x output blowing up

2005-09-24 Thread Martijn van Oosterhout
Hi, On CVS tip, whenever I do \x output, it dies with an internal error in glibc on free. If you run it under valgrind, it complains about these lines of code: 700{ 701char *my_cell = pg_local_malloc(cell_w[i] + 1); 702 703 [Inv write 1 byte] strcpy(m