🚀 go-pugleaf

In article <01HW.B6BCA545000D8F0003AD3FF0@news.panix.com>,
 Adam Wildavsky <adam@tameware.com> wrote:

>I've encountered a puzzling error. When I launch my application under 
>the Metrowerks debugger I get one of the following two messages:
>
>    The version of the symbolics file is unsupported.
>
>    Warning - this SYM file has some invalid or inconsistent data.

[snip]

One thing I would consider would be diffing the file on the FW disk with 
a copy on the ATA disk, to see if any other utility sees them as 
different. That would eliminate CW from the equation.

Hth

meeroh

>To summarize, the problem occurs with the following:
>
>CW Pro 6 or 6.1
>Apple Firewire extensions 2.5 or 2.7
>MacOS 9.1
>A FireWireDirect external hard drive
>
>Any ideas what might be going on here? I reported the problem to 
>Metrowerks and FirewireDirect a week ago - I haven't heard back from 
>either.
-- 
The contents of text files in a folder called "Random Signatures" in your Preferences folder are used as random signatures.

In article <01HW.B6BCA545000D8F0003AD3FF0@news.panix.com>, Adam Wildavsky
<adam@tameware.com> wrote:

>I've encountered a puzzling error. When I launch my application under 
>the Metrowerks debugger I get one of the following two messages:
>
>    The version of the symbolics file is unsupported.
>
>    Warning - this SYM file has some invalid or inconsistent data.
>
>I'm using CW Pro 6 under MacOS 9.1. My project folder is installed on a 
>Firewire drive from FirewireDirect.com. Disk First Aid reports no 
>errors. I can reproduce the problem 100% of the time using the Code 
>Warrior Stationery Mac C++ Toolbox project. The problem is the same for 
>68K, PPC, and Carbon targets.
>
>Applying the CW Pro 6.1 update made no difference. Using a different 
>Mac made no difference.

6.1 is just a minor IDE update that fixes some keybinding problems.
 
>Any ideas what might be going on here? I reported the problem to 
>Metrowerks and FirewireDirect a week ago - I haven't heard back from 
>either.

I imagine we'd need to get a firewire drive in order to test this.  did
you happen to send in the symbolic files that were generated on the
firewire device when you submitted your bug report?

Ron

-- 
                        GeekWare !!!
http://www.metrowerksstore.com/metrowerks/geekware.html

METROWERKS - Ron Liechty - MWRon@metrowerks.com

[[ This message was both posted and mailed: see
   the 'To' and 'Newsgroups' headers for details. ]]

On Fri, 23 Feb 2001 23:46:39 -0500, meeroh wrote
(in message <macdev-5FB6B3.23463923022001@senator-bedfellow.mit.edu>):

> One thing I would consider would be diffing the file on the FW disk with 
> a copy on the ATA disk, to see if any other utility sees them as 
> different. That would eliminate CW from the equation.

Thanks for the quick followup, Miro!

I can't usefully compare the files produced on the different drives, I 
expect because the SYM file format contains timestamps or some such. 
Fortunately I don't need to. If I copy the project folder including the 
xSYM file from one drive to another then MPW's 'equal' reports that the 
files are identical. Debugging still works only on the non-Firewire 
drive.

On Sat, 24 Feb 2001 17:23:47 -0500, MWRon wrote
(in message <mwron-2402011723470001@c243286-a.bcreek1.mi.home.com>):

Nice to hear from you Ron!

> I imagine we'd need to get a firewire drive in order to test this.

I imagine you'd need one from FirewireDirect. I'd hope they'd be 
willing to loan you one in an effort to track the problem down.

> Did you happen to send in the symbolic files that were generated on the
> firewire device when you submitted your bug report?

I didn't, but I don't need to generate the xSYM file on the firewire 
device to see the error. All I need to do is open it from the firewire 
device.

...

I do have one new datum to report. I can debug on the Firewire drive if 
I connect it to a Firewire Powerbook. My guess is that the relevant 
difference is the processor.

To resummarize, the problem occurs with the following:

CW Pro 6 or 6.1
Apple Firewire extensions 2.5 or 2.7
MacOS 9.1
A FirewireDirect external hard drive
A G4 Macintosh

-- 
Adam Wildavsky <adam@tameware.com>

In article <01HW.B6BEDD380004640B0795D210@news.panix.com>,
 Adam Wildavsky <adam@tameware.com> wrote:

>
>> Did you happen to send in the symbolic files that were generated on the
>> firewire device when you submitted your bug report?
>
>I didn't, but I don't need to generate the xSYM file on the firewire 
>device to see the error. All I need to do is open it from the firewire 
>device.
>
>...
>
>I do have one new datum to report. I can debug on the Firewire drive if 
>I connect it to a Firewire Powerbook. My guess is that the relevant 
>difference is the processor.
>
>To resummarize, the problem occurs with the following:
>
>CW Pro 6 or 6.1
>Apple Firewire extensions 2.5 or 2.7
>MacOS 9.1
>A FirewireDirect external hard drive
>A G4 Macintosh

It still would be useful to see if they were exactly the same or had 
differences for any reason.

You might want to send in an amended report if you have a clearer 
picture of when it happens.

Ron

-- 
                        GeekWare !!!
http://www.metrowerksstore.com/metrowerks/geekware.html

METROWERKS - Ron Liechty - MWRon@metrowerks.com