Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Error while loading shared libraries Post 302891068 by bphqk3 on Monday 3rd of March 2014 03:49:10 PM
Old 03-03-2014
You are incredible. Thank you so much!
 

10 More Discussions You Might Find Interesting

1. Programming

Shared libraries

Hello everybody, I am having major problems at the moment with shared libraries and I have to little knowledge of them to solve them. So please, please help me :) Ok this is the problem: I have a library A, which uses B and C, and C uses again D. If I try to run A as plugin in apache,... (0 Replies)
Discussion started by: Micky
0 Replies

2. Programming

shared libraries

I am compiling code which produces .a and .la libraries. How can I produce .so libraries? I know that gcc -shared does but how? (2 Replies)
Discussion started by: thalex
2 Replies

3. UNIX for Dummies Questions & Answers

Clarification about shared Libraries

I have a doubt about the shared libraries. Where do you set the path for the shared libaries, for the dynamic loader to locate. Any suggestion would be of great help. thanks (3 Replies)
Discussion started by: ramkumar_gr
3 Replies

4. HP-UX

Loading shared Libraries dynamically

HI, I am dynamically loading shared libraries using shl_load(). There are multiple processes (50 or more) which loads the same shared library. Will Unix internally load only one copy of the shared library or it will load multiple copies. Can I have memory issues if this is done. Thanks,... (1 Reply)
Discussion started by: Debasisb2002
1 Replies

5. Linux

Shared Libraries

How do i make a library shared say i have a library a.so which i have just compiled. I want to make it shared how do i make it Next Queation is what is the difference between a.so.0 a.so.1 a.so.2 & a.so :rolleyes: (1 Reply)
Discussion started by: wojtyla
1 Replies

6. Red Hat

RHEL5 reboot - error loading shared library

Hi All, I have RHEL 5 installed in my system. Something must has happened because when i reboot the server, it came with many error.. /usr/bin/rhgb-client -- error while loading shared libraries: libpopt.so.0. Can't open shared object files. No such file/directory It finnaly ends with the... (0 Replies)
Discussion started by: c00kie88
0 Replies

7. Ubuntu

error while loading shared libraries: libxerces-c.so.28

Hi, Can any one help me ,how to rectify the below problem?........ "error while loading shared libraries: libxerces-c.so.28: cannot open shared object file: No such file or directory" Im using "ubuntu 10.04" (64 bit) (0 Replies)
Discussion started by: kavi.mogu
0 Replies

8. Linux

xz: error while loading shared libraries: liblzma.so.5

Help! I'm busy working on MySQL replication for the site and trying to unzip this bind-geodns xz file on Linux (ubuntu) and am having some problems. http://distro.ibiblio.org/pub/linux/distributions/archlinux/community/os/i686/bind-geodns-9.4.1-4-i686.pkg.tar.xz Could anyone kindly unzip... (4 Replies)
Discussion started by: Neo
4 Replies

9. Red Hat

/usr/bin/rhgb-client -- error while loading shared libraries: libpopt.so.0

Hi All, I have RHEL 5 installed in my system. Something must has happened because when i reboot the server, it came with many error.. /usr/bin/rhgb-client -- error while loading shared libraries: libpopt.so.0. Can't open shared object files. No such file/directory It finnaly ends with the... (6 Replies)
Discussion started by: IgnitedMind
6 Replies

10. Programming

Error while loading shared libraries

I am trying to run a C++ program which uses a static library libprun.a. During compilation, I am loading this library file using a environment variable as below. LIBDIR = ${CUSTOM_PATH}/lib LOADLIBS = $(LIBDIR)/libgqlcomm.a \ $(LIBDIR)/libgsml.a \ ... (7 Replies)
Discussion started by: vdivb
7 Replies
Paranoid::Debug(3pm)					User Contributed Perl Documentation				      Paranoid::Debug(3pm)

NAME
Paranoid::Debug - Trace message support for paranoid programs VERSION
$Id: Debug.pm,v 0.93 2010/06/03 18:58:30 acorliss Exp $ SYNOPSIS
use Paranoid::Debug; PDEBUG = 1; PDMAXINDENT = 40; PDPREFIX = sub { scalar localtime }; pdebug("starting program", 1); foo(); sub foo { pdebug("entering foo()", 2); pIn(); pdebug("someting happened!", 2); pOut(); pdebug("leaving w/rv: $rv", 2): } perror("error msg"); # Deprecated psetDebug(@ARGV); DESCRIPTION
The purpose of this module is to provide a barely useful framework to produce debugging output. With this module you can assign a level of detail to pdebug statements, and they'll only be displayed when PDEBUG is set to that level or higher. This allows you to have your program produce varying levels of debugging output. Using the pIn and pOut functions at the beginning and end of each function will cause debugging output to be indented appropriately so you can visually see the level of recursion. NOTE: This module provides a function called perror which conflicts with a similar function provided by the POSIX module. If you use this module you should avoid using or importing POSIX's version of this function. NOTE: All modules within the Paranoid framework use this module. Their debug levels range from 9 and up. You should use 1 - 8 for your own modules or code. SUBROUTINES
/METHODS PDEBUG PDEBUG is an lvalue subroutine which is initially set to 0, but can be set to any positive integer. The higher the number the higher the level of pdebug statements are printed. PDMAXINDENT PDMAXINDENT is an lvalue subroutine which is initially set to 60, but can be set to any integer. This controls the max indentation of the debug messages. Obviously, it wouldn't help to indent a debug message by a hundred columns on an eighty column terminal just because your stack depth gets that deep. PDPREFIX PDPREFIX is also an lvalue subroutien and is set by default to a subroutine that returns as a string the standard prefix for debug messages: [PID - DLEVEL] Subroutine: Assigning another subroutine reference to a subroutine can override this behavior. perror perror("error msg"); This function prints the passed message to STDERR. pdebug pdebug("debug statement", 3); This function is called with one mandatory argument (the string to be printed), and an optional integer. This integer is compared against PDEBUG and the debug statement is printed if PDEBUG is equal to it or higher. The return value is always the debug statement itself. This allows for a single statement to produce debug output and set variables. For instance: Paranoid::ERROR = pdebug("Something bad happened!", 3); pIn pIn(); This function causes all subsequent pdebug messages to be indented by one additional space. pOut pOut(); This function causes all subsequent pdebug messages to be indented by one less space. psetDebug psetDebug(@ARGV); This function extracts all ^-v+$ arguments from the passed list and counts the number of 'v's that result, and sets PDEBUG to that count. You would typically use this by passing @ARGV for command-line programs. NOTE: This was a dumb idea of incredible proportions. As soons as it is safe to do so I will kill this function and perform my penance before the gods of bitrot. Consider this deprecated. DEPENDENCIES
Paranoid BUGS AND LIMITATIONS
perror (and by extension, pdebug) will generate errors if STDERR is closed elsewhere in the program. There is also no upper limit on how much indentation will be used by the program, so if you're using pIn in deeply recursive call stacks you can expect some overhead due some rather large strings being bandied about. AUTHOR
(c) 2005 Arthur Corliss (corliss@digitalmages.com) LICENSE AND COPYRIGHT
This software is licensed under the same terms as Perl, itself. Please see http://dev.perl.org/licenses/ for more information. (c) 2005, Arthur Corliss (corliss@digitalmages.com) perl v5.14.2 2010-06-03 Paranoid::Debug(3pm)
All times are GMT -4. The time now is 10:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy