Terry Lee Tucker <[EMAIL PROTECTED]> writes:
> The alternate input source is created on application startup with:
> ctrl->sys->dbInputId = XtAppAddInput (app,
> ctrl->sys->socketId,
> (XtPointer) (XtInputReadMask),
> DbInputCB, (XtPointer) ctrl);
> And, it remain
Tom,
The alternate input source is created on application startup with:
ctrl->sys->dbInputId = XtAppAddInput (app,
ctrl->sys->socketId,
(XtPointer) (XtInputReadMask),
DbInputCB, (XtPointer) ctrl);
And, it remains throughout the duration of the application. I bel
Terry Lee Tucker <[EMAIL PROTECTED]> writes:
> Sorry, I didn't know what you needed. Here is the trace:
> (gdb) bt
> #0 0x2b04eef2 in select () from /lib/i686/libc.so.6
> #1 0x2adeb06c in ?? () from /usr/X11R6/lib/libXt.so.6
> #2 0x0001 in ?? ()
> #3 0x08136b88 in ?? ()
> #4 0x2adc0c47 in
Sorry, I didn't know what you needed. Here is the trace:
(gdb) bt
#0 0x2b04eef2 in select () from /lib/i686/libc.so.6
#1 0x2adeb06c in ?? () from /usr/X11R6/lib/libXt.so.6
#2 0x0001 in ?? ()
#3 0x08136b88 in ?? ()
#4 0x2adc0c47 in XtChangeManagedSet () from /usr/X11R6/lib/libXt.so.6
#5 0x
Terry Lee Tucker <[EMAIL PROTECTED]> writes:
>> Is this a bug? Did anybody look at the stack trace is sent? I don't have
>> the expertise to analyze it.
I haven't seen any stack trace. strace is not a stack trace --- I'm
talking about attaching to the stuck process with gdb and getting the
resul
I realize that I'm carrying on a conversation with myself here; however,
nothing new 'bout that, I do it all the time ;o)
Just in case anyone else is interested, the only way I can get this to work
correctly is to put a 100 millisecond timer in front of the call to
CheckForNotifies as in:
This thing is hanging up in PQnotifies. I have added a simple fprintf
statement to the following function:
void CheckForNotifies (Controls *ctrl)
{
#ifndef CALL_TRACE
fprintf (stderr, "%s: %d: %s (%s)\n", __FILE__, __LINE__,
__FUNCTION__, ctrl->table);
#endif
PQflush (ctrl->sy
See partial output from strace below. On this particular run, the command
locked up during the second edit operation. The notify message, move_update,
was delivered, but the PQsendquery never returns.
Any ideas Tom?
recv(3, "A\0\0\0\25\0\0~3move_update\0\0C\0\0\0\rUPDAT"..., 16384, 0) = 42
writ
Thanks for the reply Tom. See comments below:
On Thursday 24 February 2005 12:06 pm, Tom Lane saith:
> Terry Lee Tucker <[EMAIL PROTECTED]> writes:
> > All this works great except for certain cases where one of the notify
> > messages, the one I'm really interested in, gets spooled, queued, or
> >
Terry Lee Tucker <[EMAIL PROTECTED]> writes:
> All this works great except for certain cases where one of the notify
> messages, the one I'm really interested in, gets spooled, queued, or
> something and is not delivered until I send another notification, after the
> fact, from another client; t
Hello List:
I am working on the proper method for Notification processing. The application
interface is X-Windows and I am using the database socket as an alternate
input source to the X-Server. I have a callback that fires when there is data
to read on the socket. Here is the setup:
/* This c
11 matches
Mail list logo
