Обсуждение: Problems with pg_dump for PG8.4 for WinXP (MinGW build)
Hello! I need PG 8.4 built from source code for WinXP. So I got archive postgresql-8.4.1.tar.gz, unpacked it and built postgresby MinGW, as usual: configure --witout-zlib make make install Everything seeds to be fine until we tried to test pg_dump. It failed (not always but often). Command: pg_dump -U postgres -v -f mydump.sql TEST_DB The end of output: pg_dump: reading triggers for table "test_table" pg_dump: reading dependency data pg_dump: saving encoding = UTF8 pg_dump: saving standard_conforming_string = off pg_dump: saving database definition And here we get a message 'an unhandled win32 exception occured in pg_dump.exe(1788)' (digits in brackets varies for different runs of pg_dump) There are no such problems for ready biniries. Regards, Marina.
2009/9/15 el dorado <do_ra_do@mail.ru>: > Hello! > I need PG 8.4 built from source code for WinXP. So I got archive postgresql-8.4.1.tar.gz, unpacked it and built postgresby MinGW, as usual: > configure --witout-zlib > make > make install > > Everything seeds to be fine until we tried to test pg_dump. It failed (not always but often). > Command: > pg_dump -U postgres -v -f mydump.sql TEST_DB > > The end of output: > pg_dump: reading triggers for table "test_table" > pg_dump: reading dependency data > pg_dump: saving encoding = UTF8 > pg_dump: saving standard_conforming_string = off > pg_dump: saving database definition > > And here we get a message 'an unhandled win32 exception occured in pg_dump.exe(1788)' > (digits in brackets varies for different runs of pg_dump) > > There are no such problems for ready biniries. Given that, it seems to be something with your mingw setup causing it. I think you'll have to get yourself a backtrace using gdb (the native debugger tools can usually not get usable backtraces from a a mingw build). -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
> 2009/9/15 el dorado <do_ra_do@mail.ru>: > > Hello! > > I need PG 8.4 built from source code for WinXP. So I got archive postgresql-8.4.1.tar.gz, unpacked it and built postgresby MinGW. > > Everything seeds to be fine until we tried to test pg_dump. It failed (not always but often). > > Command: > > pg_dump -U postgres -v -f mydump.sql TEST_DB > > And here we get a message 'an unhandled win32 exception occured in pg_dump.exe' > Given that, it seems to be something with your mingw setup causing it. > I think you'll have to get yourself a backtrace using gdb (the native > debugger tools can usually not get usable backtraces from a a mingw > build). > Magnus Hagander Hello! Thank you very much for your answer. I try to use gdb now. But there is a little difficulty. I'm not quite sure it is connectedwith postgres build. Probably I do something wrong using gdb but maybe you could show me the direction for resolvingthe problem? I built PostgreSQL 8.4 (WinXP, MinGW) with following configuration options: configure --without-zlib --enable-debug --enable-cassert --enable-depend So I supposed the result should include debugging symbols. But I don't see the function names in the backtrace. It looks like: (gdb) bt #0 0x7c8106e9 in ?? () #1 0x00000000 in ?? () (gdb) Maybe you could advise me how to get more detailed information? I'll appreciate any help. Regard, Marina.
> Hello! > Thank you very much for your answer. I try to use gdb now. But there is a little difficulty. I'm not quite sure it is connectedwith postgres build. Probably I do something wrong using gdb but maybe you could show me the direction for resolvingthe problem? > I built PostgreSQL 8.4 (WinXP, MinGW) with following configuration options: > configure --without-zlib --enable-debug --enable-cassert --enable-depend > So I supposed the result should include debugging symbols. > But I don't see the function names in the backtrace. It looks like: > (gdb) bt > #0 0x7c8106e9 in ?? () > #1 0x00000000 in ?? () > (gdb) > Maybe you could advise me how to get more detailed information? > I'll appreciate any help. Hello! Sorry for disturbing. I've found out what was the problem. I should set CFLAGS in configuration options. Now there is the following: configure --without-zlib --enable-debug --enable-cassert --enable-depend CFLAGS='-Zi -g' Regards, Marina.