> So, does anyone out there regularly run multiple copies of POSE at once?

This may be a more common occurence in the future.  The next public release of
Poser will support the ability to redirect serial communications over a TCP
connection.  Thus, you can run two versions of Poser and have them exchange data
with each other -- even beam to each other (by using Shortcut-S to switch IR
transmission over the serial port, but *not* using Shortcut-T to put IR into
loopback mode).

-- Keith Rollin
-- Palm OS Emulator engineer





Warren Young <[EMAIL PROTECTED]> on 02/25/2001 07:57:00 PM

Please respond to "Palm Developer Forum" <[EMAIL PROTECTED]>

Sent by:  Warren Young <[EMAIL PROTECTED]>


To:   "Palm Developer Forum" <[EMAIL PROTECTED]>
cc:    (Keith Rollin/US/PALM)
Subject:  Re: I broke debugging somehow, gdb, Pose



[EMAIL PROTECTED] wrote:
>
> > What in the world did I do to break this?
>
> Beats me.  Turn on High- and Low-level debugger logging, do the same thing

Sorry for taking so long to get back to you on this, but in my copious
weekend hacking time, I did finally figure out what was going wrong.
There was another copy of POSE running in the background, unbeknownst to
me.  Since this machine has been up for about 2 months continuously now,
there's no telling when it started or what caused it to lose its X
window but still remain running in the background.  The background copy
of POSE had the debugger ports open, so POSE couldn't bind() to the
port, and gdb was connecting to the wrong copy of POSE.

The bind() call in SocketMessaging.cpp must have been failing on the
second invocation of POSE, but this will only cause an optional log
message.  I wonder if this is a case where the user needs to be warned
in a message box.  Normally, that bind() should succeed every time.  (If
another program is using the ports, and it's not another copy of POSE,
then you just need to change the debugger port in your preferences.)

So, does anyone out there regularly run multiple copies of POSE at
once?  If so, promoting the bind() failure to a popup warning would be
annoying, without some additional infrastructure like a semaphore that
the first copy of POSE creates, and subsequent copies check to see if
another copy of POSE is running.
--
= Warren Young -- Maintainer of the Palm OS Programmer's FAQ at:
=     http://www.cyberport.com/~tangent/palm/faq/
=
= ICBM Address: 36.8274040 N, 108.0204086 W, alt. 1714m

--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/tech/support/forums/





-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/

Reply via email to