Hi listers,
I just re-joined the list after some years of not programming for OS X, and today encountered something strange while re-familiarizing myself.
Was going through Second Edition of Aaron Hillegas's Cocoa book (yes, I know it's waaaay out of date, but I'm not finding it too difficult to make the impedance match with Xcode 4.1, though I look forward to and will buy his new edition), and in Chapter 9, after adding an NSColorWell/IBAction to the app's preferences pane, and after clicking on it during a test run, gdb spews this:
warning: Could not find object file "/Users/lindberg/BlackOps/Source/Modules/RCWebColorPicker/build/RCWebColorPicker.build/Deployment/RCWebColorPicker.build/Objects-normal/x86_64/RCWebColorPicker.o" - no debug information available for "/Users/lindberg/BlackOps/Source/Modules/RCWebColorPicker/RCWebColorPicker.m".
Searched xcode-users list for BlackOps, nothing. Google shows a report (seemingly repeated a few times, from the same Carsten Bormann) with an identical gdb log: GNU bug report logs - #65523.0.60; (NS/OSX:) Colorpicker, Menu abort() in eval()Date: Wed, 6 Aug 2008 06:05:06 UTC 1) Tried the color picker from the Emacs Preferences (OSX 10.5.4; run - Q), crash on OK in the preferences panel. 2) Most menu entries (e.g., Options) crash in the same place immediately upon clicking them.
with no resolution, just some questions from one of the GNU emacs team. But very similar, color picker in preferences in an OS X app. But 3 years ago.
100% repeatable for me. Seen on both 10.7.1/Xcode 4.1 and 10.6.8/Xcode 4.02, though there's a detail: I normally build it on 10.7.1, it works the same when that build is run on both computers (10.7.1 and 10.6.8) under Xcode, but if I clean and build on 10.6.8, it doesn't show the message. I haven't asked for any special linking or anything, just taking the defaults.
No obvious ill effects to the app, but seeing a user name and BlackOps is unnerving and may indicate something untoward on my system.
It may be harmless, just that some engr left an absolute link path in code he shouldn't have (I've done that in generic UN*X), but this report is 3 years old. Shoulda been fixed by now.
Does anyone here know what this is, and whether it represents an invasion of my system?
Many Thanks,
ScottB |