shared libs and bad magic number

what can typically cause a bad magic number on a shared lib ?
migueAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
jlevieConnect With a Mentor Commented:
Does it give you a clue as to what shared lib it doesn't like? My suspicion is that there's either a path or filename problem and something is being specified that's not a shared lib, or that one of the shared libs is in fact bogus.

The "magic number" is just that. There's a file somewhere (perhaps in /etc or /usr/share) on your system that defines certain special numbers that will in appear in files of a specific type at a certain location(s) in the file ("man magic" should tell you more). The magic number is always used by the file(1) command when it tells you what a give file type is. Other things might use the same process to determine the validity of a file they've been given for processing, like a dynamic loader.
0
 
jlevieCommented:
In what context? Typically it would indicate something wrong with the shared lib, but it could also be a problem with how the lib is being examined.
0
 
migueAuthor Commented:
need more detailed answer, examples etc....
0
 
jlevieCommented:
Well, what are you doing when you get "bad magic number" reported?
0
 
migueAuthor Commented:
running a script thats loads some procs..to have other procs connect to oracle db on hp-ux.

I don't do anything. I just get the error and then crack open the DBA manuals.....
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.