wxSocket connect fails (wxMac 2.6.0 / CW 8.3 / unicode / mach-o target)

wxSocket connect fails (wxMac 2.6.0 / CW 8.3 / unicode / mach-o target)

Post by shrut » Thu, 29 Sep 2005 23:17:17


Hi,

I am porting Client/server application on mac using wxWidgets.

I am using wxMac 2.6.0 (unicode, Mach-o)/ CW 8.3 / Mac OS 10.3.

I tried running my client to open a socket but unfortunately, the
client returns that it cannot connect.

To make sure there isn't anything wrong on my side i tested this issue
with the socket sample provided (mach-o + unicode) but that too fails
to connect.

The socket (client) sample fails to connect only with mach-o target &
wxUSE_UNICODE flag set to 1. It works well with Carbon target.

Thanks in Advance !
-Shruti
 
 
 

1. wcsrtombs returns 0 length on CW 8.3 Mach-o target

2. Can't debug a MACH-O project in CW 8.3

Hi,

I need to debug my newly cloned MACH-O target. I can single-step the
code and the de *** window (Main Thread) is present during this. If I
run the project a "Log" window appears and the "Main Thread" window
goes away. The Log window says:

------------------------------
Debugging started for ebstofip at 11:27:55 AM
Starting Mach-o App: /Volumes/Our
Stuff/alen/admin/ICGS/consulting/MTi/shared modules/ipmerge/ebstofip
=shlibs-updated
ebstofip: TCID MSFX set [ipmerge_InitData:Tue Mar 2 16:27:59 2004
ipmerge_stubs.c(83)]
Debugging stopped for ebstofip at 11:28:00 AM

The message starting "ebstofip" is generated by my application and is
expected.

Why is the Debugging stopped? If I run the executable from a terminal I
get the expected continuation of the program past this point with lots
more output.

If I set a breakpoint in my code, I get the same "Debugging stopped"
effect. i.e. the breakpoint is not reached and the program terminates
with no explanation.

I do not know how to proceed at this point :-(. I'm going to rebuild
all the pre-compiled headers and libraries again just in case my
original 8.3 upgrade was not correctly done (over a year ago (who can
remember that far back?)).

Suggestions anyone?

TIA
--alen

3. CW 8.3 Mach-O ppc/ansi.h problem

4. CW 8.3 Mach-o Linker options

5. Tip - slow linking of Mach-O apps in CW 8.3

6. CW 8.3 useless for building mach console applications?

7. debug Mach-O iMovie plugin 8.3

8. Still struggling with Mach-O and MSL in CodeWarrior 8.3 on Mac OS X

9. Compile errors using 8.3, Mach-O, newer builds of OS X

10. CW 8.3 crashing when ANY CW window is resized - OS X 10.3.3

11. CW 8.3/CW 9.4 Mac OS X 10.4 problem

12. Debugger doesn't connect in CW 8.3 all of a sudden

13. [Q] CW 9 Mach-O debug doesn't stop at breakpoints.

14. CW 7 Mach-O link error on MacOS X.2.8

15. CW 9.6 doesn't set creator/type of Mach-O executable?