[PD-dev] [ pure-data-Bugs-1724027 ] netsend connect error not displayed in main window in winXP

[SourceForge.net]

Bugs item #1724027, was opened at 2007-05-23 11:57
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1724027&group_id=55736

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: v0.40.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Matteo Sisti Sette (sistisette)
Assigned to: Nobody/Anonymous (nobody)
Summary: netsend connect error not displayed in main window in winXP

Initial Comment:
Hi,

I don't know whether this is Windows-specific: only tested it on Windows XP.

In Windows, PD's errors and system messages (as well as [print] outputs) are usually displayed in the main PD window (the one with the "DIO errors" button and "compute audio" checkbox etc.)

However, when a [connect( message is sent to a [netsend] object and the connection cannot be established because nobody is listening to the port (but the host does exist), the following error:

"Connecting stream socket: Unknown error (10061)"

is not displayed in the main window. If running pd from line command, the message is displayed in the dos window. If running PD "directly" without dos window, the error message is not displayed at all.

I guess the message is sent to the stdout or stderr instead of being correctly "catched" and displayed in the main window.
The problem is that no error message at all is displayed in the main window.

Try this to reproduce the bug:

[connect localhost 5000(
|
[netsend]

obviously, with nobody listening to port 5000.


When the host itself is unreachable, a "bad host?" message is correctly displayed in the main window, so the following WON'T reproduce the bug:

[connect badhostname 5000(
|
[netsend]

----------------------------------------------------------------------

>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-10-16 14:27

Message:
Logged In: YES 
user_id=564396
Originator: NO

the problem here is that the error-message is not output by Pd itself but
rather by the underlying library that provides the networking stuff.
this output is sent to stderr directly (and not to Pd which can then
decide where to put it)

a solution for this would be to re-direct the stderr (and stdout when we
are there...) to the pd-console;
i have no idea how to do that.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1724027&group_id=55736