🚀 go-pugleaf

Well about an hour after sending that email I got the dev cd and installed
it. Basically getting the same problem with the official version of gdb
instead of the one ripped from the Darwin CD.

CodeWarrior still won't connect to MetroNubX. So I went back to CWPro5
methods. I launched DebugNub manually and it connected to port 6969. So I
connect from CW to 127.0.0.1:6969 and it actually connects and uploads the
software. Crazy.

Is something weird going on? Has _ANYONE_ gotten CWPro6 to debug Carbon
apps?

    Jon.

executing command: "file /Developer/Tools/LaunchCFMApp\n"
awaiting response: "\n[0x1a][0x1a]prompt\n"
raw data: "file 
/Developer/Tools/LaunchCFMApp\n\n[0x1a][0x1a]post-prompt\nReading symbols
from 
/Developer/Tools/LaunchCFMApp...done.\n\n[0x1a][0x1a]breakpoints-invalid\n\n
[0x1a][0x1a]pre-prompt\n(gdb) \n[0x1a][0x1a]prompt\n"
annotation 0: "\n[0x1a][0x1a]post-prompt\nReading symbols from
/Developer/Tools/LaunchCFMApp...done."
annotation 1: "\n[0x1a][0x1a]breakpoints-invalid"
annotation 2: "\n[0x1a][0x1a]pre-prompt\n(gdb)"
annotation 3: "\n[0x1a][0x1a]prompt\n"
received message:
{
              length: 14
          message-id: kLaunchFragmentMessage (0x8c)
         fragment-id: 0x1000
          background: no
}
error on line 653 of "DebugNub/GDBConnection.cc" in function "enum GDBError
GDBConnection::Launch(long unsigned int)": assertion failed: "fragment !=
NULL"; going to fail_bad_fragment
error on line 873 of "DebugNub/ClientConnection.cc" in function "int
ClientConnection::DoLaunchFragment(MetroNubRemoteMessageHeader *, void *,
MetroNubRemoteReplyHeader *, void *)": assertion failed: "gdbNoErr ==
result"; going to fail_launch
sending message:
{
              length: 12
          message-id: kGenericReply (0x64)
               error: 1
}
received message:
{
              length: 12
          message-id: kClearBreakPointMessage (0x77)
       breakpoint-id: 1
}
executing command: "delete 1\n"
awaiting response: "\n[0x1a][0x1a]prompt\n"
raw data: "delete 1\n\n[0x1a][0x1a]post-prompt\nNo breakpoint number
1.\n\n[0x1a][0x1a]pre-prompt\n(gdb) \n[0x1a][0x1a]prompt\n"
annotation 0: "\n[0x1a][0x1a]post-prompt\nNo breakpoint number 1."
annotation 1: "\n[0x1a][0x1a]pre-prompt\n(gdb)"
annotation 2: "\n[0x1a][0x1a]prompt\n"
sending message:
{
              length: 12
          message-id: kGenericReply (0x64)
               error: 1
}



On 9/22/00 12:13 PM, in article B5F0FD6A.41F%JWight@bigfoot.com, "Jonathan
Wight" <JWight@bigfoot.com> wrote:

> Hey,
> 
> Well I just found the thread on failure to debug in CW6 and PB1. I'm in the
> same situation but the actual details are similar...
> 
> I installed the gdb and other Darwin dev stuff from the latest Darwin disk
> image. When trying to debug using CWPro6, MetroNubX does launch and CWPro6
> beachballs for about a minute then fails with a "Network Timeout Error". I
> tried setting the debugging ports manually using the debug preferences but
> got the same error.
> 
> Theoretically I should have all the tools I need to debug with CWPro6 but it
> ain't working. Has anyone gotten CWPro6 to debug successfully, and
> especially with the Darwin dev tools.
> 
>   Jon.
> 
> Now when the heck is my OSX dev CD coming?
> 

Jonathan Wight <JWight@bigfoot.com> wrote:

> Hey,
> 
> Well I just found the thread on failure to debug in CW6 and PB1. I'm in the
> same situation but the actual details are similar...
> 
> I installed the gdb and other Darwin dev stuff from the latest Darwin disk
> image. When trying to debug using CWPro6, MetroNubX does launch and CWPro6
> beachballs for about a minute then fails with a "Network Timeout Error". I
> tried setting the debugging ports manually using the debug preferences but
> got the same error.
> 
> Theoretically I should have all the tools I need to debug with CWPro6 but it
> ain't working. Has anyone gotten CWPro6 to debug successfully, and
> especially with the Darwin dev tools.
> 
>     Jon.
> 
> Now when the heck is my OSX dev CD coming?

The beta has a showstopper in that PPP connections are invisible to
classic applications. If you have PPP running rather than a network
connection, CW 6 may not be able to see the network.

-- 
Harry Erwin, PhD, <mailto:herwin@gmu.edu>,Computational Neuroscientist 
(modeling bat behavior) and Senior SW Analyst and Security Engineer. 
Looking--CV available at: <http://mason.gmu.edu/~herwin/CV.htm>

In article <1ehitpe.ud8tmhuwadkwN%herwin@gmu.edu>, herwin@gmu.edu 
(Harry Erwin) wrote:

>The beta has a showstopper in that PPP connections are invisible to
>classic applications. If you have PPP running rather than a network
>connection, CW 6 may not be able to see the network.

Do you mean Carbon instead of classic? CW 6 is a native Carbon app, so I 
would be surprised if classic is a factor.

--
Brad Oliver
bradman@pobox.com.AM_SPAY

in article 1ehitpe.ud8tmhuwadkwN%herwin@gmu.edu, Harry Erwin at
herwin@gmu.edu wrote on 9/25/00 3:32 PM:

>> Hey,
>> 
>> Well I just found the thread on failure to debug in CW6 and PB1. I'm in the
>> same situation but the actual details are similar...
>> 
>> I installed the gdb and other Darwin dev stuff from the latest Darwin disk
>> image. When trying to debug using CWPro6, MetroNubX does launch and CWPro6
>> beachballs for about a minute then fails with a "Network Timeout Error". I
>> tried setting the debugging ports manually using the debug preferences but
>> got the same error.
>> 
>> Theoretically I should have all the tools I need to debug with CWPro6 but it
>> ain't working. Has anyone gotten CWPro6 to debug successfully, and
>> especially with the Darwin dev tools.
>> 
>> Jon.
>> 
>> Now when the heck is my OSX dev CD coming?
> 
> The beta has a showstopper in that PPP connections are invisible to
> classic applications. If you have PPP running rather than a network
> connection, CW 6 may not be able to see the network.

I haven't installed the tools yet from the Dev CD but I am on a straight
network, not on PPP, and I had the same problem.

--
Mike Nowak         
Health Media Research Laboratory, The University of Michigan
http://www.dentdelion.com/mike/