Showing posts with label lookup. Show all posts
Showing posts with label lookup. Show all posts
Monday, September 9, 2013
Sunday, September 8, 2013
D-U-N-S Number Lookup for Company Enrollment
After completely the 'D-U-N-S Number Lookup for Company Enrollment' form here:
https://developer.apple.com/ios/enroll/dunsLookupForm.action
I get this error message:
"We are unable to process your request.
Please go back to the previous page, or quit your browser and try your request again."
Is this problem going to be fixed? Is there any other way to get a DUNS number without having to go through D&B?
Any help/ feedback would be greatly appreciated.
Thanks!
Sunday, January 20, 2013
crash possibly due to bad symbol lookup
I have a c++ app running on OS/X Lion which crashes in a call to glIsBuffer(0). The XCode 4.5 stack trace states:
error: address doesn't contain a section that points to a section in a object file
and DYLD_PRINT_APIS shows:
dlopen(/System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphics.framework/CoreGraphics, 0x00000009) ...
dlsym(0x7f9288d00cd0, gliCopyAttributes)
dlsym(0x7f9288d00cd0, gliGetVersion) dlsym(0x7f9298d70620, __CGBitmapContextDelegateCreate)
dlsym(0xffffffffffffffff, CGSCopyCoreGraphicsCapabilities)
Segmentation fault: 11
The last call to dlsym() appears to have been passed a rather strange library handle. I looked at the return values for dlopen, but it should be returning NULL on error. There are no errors reported for the dlopen calls in the log.
CGSCopyCoreGraphicsCapabilities is a Core Graphics call, though Google doesn't turn up any docs on it. My current hypothesis is that dlsym is using an invalid library handle. Perhaps the proper Core Graphics library is not loaded or has been unloaded.
Running otool shows a few version mismatches:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0)
but I don't know enough to say whether they are relevant.
Can anyone help to decipher what might be the problem?
thanks!
Re: crash possibly due to bad symbol lookup
wrabbit99 wrote:
What do you mean by a "c++ app"? This is written in c++, has a main(), is built by a makefile, and probably does not resent being called a "c++ app".
I was making a reference to your initial categorization of your program as "a c++ app". It isn't. It is an OpenGL application written in C++, using Boost, glfw, vdb_view, valgrind, and who knows what else.
For this app, you asked for assistance in an Apple Development forum. That probably wasn't the best approach. Your app is only superficially a Mac app. You appear to have resolved the problem on your own. In the future, if you are working with specific open-source libraries using their build scripts, it would probably be best to go to the authors of those libraries first. It isn't that your questions aren't welcome here, it is just that you aren't likely to find a speedy answer here.
Re: crash possibly due to bad symbol lookup
wrabbit99 wrote:
What do you mean by a "c++ app"? This is written in c++, has a main(), is built by a makefile, and probably does not resent being called a "c++ app".
I was making a reference to your initial categorization of your program as "a c++ app". It isn't. It is an OpenGL application written in C++, using Boost, glfw, vdb_view, valgrind, and who knows what else.
For this app, you asked for assistance in an Apple Development forum. That probably wasn't the best approach. Your app is only superficially a Mac app. You appear to have resolved the problem on your own. In the future, if you are working with specific open-source libraries using their build scripts, it would probably be best to go to the authors of those libraries first. It isn't that your questions aren't welcome here, it is just that you aren't likely to find a speedy answer here.
Re: crash possibly due to bad symbol lookup
wrabbit99 wrote:
What do you mean by a "c++ app"? This is written in c++, has a main(), is built by a makefile, and probably does not resent being called a "c++ app".
I was making a reference to your initial categorization of your program as "a c++ app". It isn't. It is an OpenGL application written in C++, using Boost, glfw, vdb_view, valgrind, and who knows what else.
For this app, you asked for assistance in an Apple Development forum. That probably wasn't the best approach. Your app is only superficially a Mac app. You appear to have resolved the problem on your own. In the future, if you are working with specific open-source libraries using their build scripts, it would probably be best to go to the authors of those libraries first. It isn't that your questions aren't welcome here, it is just that you aren't likely to find a speedy answer here.
Re: crash possibly due to bad symbol lookup
wrabbit99 wrote:
What do you mean by a "c++ app"? This is written in c++, has a main(), is built by a makefile, and probably does not resent being called a "c++ app".
I was making a reference to your initial categorization of your program as "a c++ app". It isn't. It is an OpenGL application written in C++, using Boost, glfw, vdb_view, valgrind, and who knows what else.
For this app, you asked for assistance in an Apple Development forum. That probably wasn't the best approach. Your app is only superficially a Mac app. You appear to have resolved the problem on your own. In the future, if you are working with specific open-source libraries using their build scripts, it would probably be best to go to the authors of those libraries first. It isn't that your questions aren't welcome here, it is just that you aren't likely to find a speedy answer here.
Subscribe to:
Posts (Atom)
