• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 563
  • Last Modified:

shared libs and bad magic number

what can typically cause a bad magic number on a shared lib ?
0
migue
Asked:
migue
  • 3
  • 2
1 Solution
 
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
 
jlevieCommented:
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

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now