| From: | "Cyril VELTER" <cyril(dot)velter(at)metadys(dot)com> | 
|---|---|
| To: | magnus(at)hagander(dot)net | 
| Cc: | pgsql-general(at)postgresql(dot)org | 
| Subject: | [Re] Re: [Re] Re: Winsock error 10035 while trying to upgrade from 8.0 to 8.2 | 
| Date: | 2007-05-22 21:18:31 | 
| Message-ID: | 0-39224874141-2674-1814223@CFGEM | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
> Cyril VELTER wrote:
> > 	No I'm not. It's not even complied in the server nor in the pg_dump 
binary.
> > 
> > 	The server is built on windows using MSYS simply with ./configure && make 
all 
> > && make install
> > 	
> > 
> > 	I've been able to reproduce the problem 6 times (at random points in the 
> > process, but it never complete successfully). Is there any test I can do to 
> > help investigate the problem ?
> 
> Sorry I haven't gotten back to you for a while.
> 
> Yeah, if you can attach a debugger to the backend (assuming you have a
> predictable backend it happens to - but if you're loading, you are using
> a single session, I assume?), add a breakpoint around the area of the
> problem, and get a backtrace from exactly where it shows up, that would
> help.
	Thanks for your reply. I'll try to do this. I've installed gdb on the 
problematic machine and recompiled postgres with debug symbols (configure 
--enable-debug)
	I'm not very familiar with gdb. Could you give some direction on setting the 
breakpoint. After running gdb on the postgres.exe file, I'm not able to set the 
breakpoint (b socket.c:574 give me an error).
	Searching the source files, it seems the error message is generated in 
port/win32/socket.c line 594.
Thanks,
cyril
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Reyes | 2007-05-22 22:07:35 | Command line export or copy utility? | 
| Previous Message | Mage | 2007-05-22 20:49:20 | partial word matching |