Corinna Vinschen wrote:
> No more debugging necessary. I found the cause of the problem. At one
> point the file attributes were not correctly stored for socket files and
> when postgres touches the socket file (which it does every 5 minutes),
> the correct file attributes got lost. Especially
On May 9 20:45, Krzysztof Duleba wrote:
> I turned off all non-system apps except for cygserver and postgresql and
> still the same.
>
> How can I provide more debug info? Is it possible to check which processes
> access or modify the socket file?
No more debugging necessary. I found the cause
Corinna Vinschen wrote:
> On May 6 02:02, Krzysztof Duleba wrote:
> > 150 int issocket () const {return dev.devn == FH_UNIX;}
> > (gdb) n
> > 78set_errno (EBADF);
> > (gdb) n
> > 79return 0;
>
> Your debugging shows that my assumption was correct. The file i
On May 6 02:02, Krzysztof Duleba wrote:
> 150 int issocket () const {return dev.devn == FH_UNIX;}
> (gdb) n
> 78set_errno (EBADF);
> (gdb) n
> 79return 0;
Your debugging shows that my assumption was correct. The file isn't
recognized as socket anymore. This
Christopher Faylor wrote:
> This isn't really a "how do I debug the dll" It's a "how do I debug".
That, too.
> gdb psql.exe
> dll cygwin1.dll
> l get_inet_addr
> bp
> run
Thanks. Assuming that bp should read break (undefined command otherwise)
gdb produced the following output:
Bre
On Thu, May 05, 2005 at 11:10:30PM +0200, Krzysztof Duleba wrote:
>Corinna Vinschen wrote:
>
>> Are you set up to debug the DLL using GDB? If you download the latest
>> snapshot from http://cygwin.com/snapshots and set a breakpoint to
>> get_inet_addr, you could step through this function until it
Corinna Vinschen wrote:
> Are you set up to debug the DLL using GDB? If you download the latest
> snapshot from http://cygwin.com/snapshots and set a breakpoint to
> get_inet_addr, you could step through this function until it's left.
> The first interesting information would be, from which line
On May 3 22:12, Krzysztof Duleba wrote:
> Corinna Vinschen wrote:
>
> > I have the strange feeling that the file isn't recognized as socket
> > anymore for some reason. When you called `cat /tmp/.s.PGSQL.5432',
> > did you use Cygwin's cat? If the file would have been recognized as
> > socket,
Corinna Vinschen wrote:
> I have the strange feeling that the file isn't recognized as socket
> anymore for some reason. When you called `cat /tmp/.s.PGSQL.5432',
> did you use Cygwin's cat? If the file would have been recognized as
> socket, you shouldn't have been able to read the content of t
On May 3 13:24, Krzysztof Duleba wrote:
> Corinna Vinschen wrote:
>
> > > However, `psql -h localhost -p 5432' succeeds. So in fact the socket
> is
> > > still there, but the link stored in /tmp/.s.PGSQL.5432 is broken.
> >
> > That's rather unlikely. Could you show us an strace of the above
> f
On May 3 01:26, Krzysztof Duleba wrote:
> Hi
>
> I am using Cygwin postgresql as my db engine for high load jboss/Hibernate
> web app. It works fine, but after some 10k transactions socket seems
> broken and I get this message:
>
> $ psql
> psql: could not connect to server: Bad file descriptor
11 matches
Mail list logo
