Sponsored Content
Top Forums Programming Linux: dlopen fails to find symbols Post 302422438 by DreamWarrior on Tuesday 18th of May 2010 11:38:02 AM
Old 05-18-2010
Quote:
Originally Posted by Corona688
I don't believe shared libraries are intended to be able to link backwards in that manner. If you must have the shared library call a local function, pass it as a function pointer.
But why, when I link the other library, does it work? That seems odd to me.
 

10 More Discussions You Might Find Interesting

1. HP-UX

test program(dlopen) fails on hp but run well on solaris

Hi, I have a c test program which test dlopen call. This program run well on solaris but fails on hp-ux. The program load jvm library successfully on solaris. On hp-ux it displays error I compile this program as $cc -o testjvm testjvm.c What am I missing? I have tried... (2 Replies)
Discussion started by: shriashishpatil
2 Replies

2. AIX

Find command fails in crontab

Hi , I imported find command I have on my hp-ux server to clean up the /tmp of my new IBM AIX servers. Though, the commands always fails in the cron but if I past it at the prompt, it works find. I tried with at jobs and regular 'find' . Could anyone tell me what I am doing wrong? Many... (4 Replies)
Discussion started by: cforget2810
4 Replies

3. Programming

dlopen Linux vs. OSX

I've got a C++ program and some plugins ( shared objects ) that I have been developing for Linux. I was originally using and OSX machine to develop and test most of the code. I use dlopen to open the shared objects and then call methods from them. It behaves differently on Linux ( don't know the... (3 Replies)
Discussion started by: rfkrakora
3 Replies

4. UNIX for Advanced & Expert Users

Grub installation fails in Linux BMR..

Hi all, This topic is purely on a problem in installing grub in my LINUX BMR process... A major problem too.. I am designing Linux BMR where i do the following.. Backup the " / " as a whole .. with partition details ..etc And using the Knoppix Live CD i first create the partitions... (1 Reply)
Discussion started by: selvarajvs
1 Replies

5. UNIX for Advanced & Expert Users

Difference between Unix and Linux for resolving symbols

I came across a difference between Unix and Linux, when it comes to resolving the symbols from the libs. consider the following code segments... $ cat call1.c #include <stdio.h> int a1; extern int a3; void prnt_a3() { printf("\n%d\n",a3); } $ cat test.c #include <stdio.h>... (12 Replies)
Discussion started by: snowline84
12 Replies

6. UNIX for Dummies Questions & Answers

Find command fails when a space is in the directory path variable

I have a script like this running under OS X 10.8. The problem arises when the find command encounters a space in the path name. I need the "dir" variable as I'll be extending the script to more general use. #!/bin/bash CFS=$IFS IFS=$(echo) set dir = "/Users/apta/Library/Mail\... (3 Replies)
Discussion started by: apta
3 Replies

7. UNIX for Dummies Questions & Answers

Tcp connection to Linux server fails

I am trying to send json messages to a port on a linux server from a remote server running a .net program. I have one implementation running with successful incoming messages to port 1514. I tried to replicate the same thing but just to another port but cannot get it to work as I get the following... (3 Replies)
Discussion started by: unienewbie
3 Replies

8. Shell Programming and Scripting

sed works on Linux but fails on Solaris

Hi, On Linux i get the desired ouput: echo "<value>WEB_USER</value>" | sed 's/\(<value>\|<\/value>\)//g'Output: Executing the same command on Solaris: echo "<value>WEB_USER</value>" | sed 's/\(<value>\|<\/value>\)//g'Output: I need to get the desired output on Solaris i.e. WEB_USER and... (4 Replies)
Discussion started by: mohtashims
4 Replies

9. Shell Programming and Scripting

find command fails mid-way during execution

I wish to search for a particular string say "Yellow_Colors" in all files in all folders in the current directory. Below is the command I use: find ./ -type f | xargs grep -i "Yello_Colors"However, my command does not traverse all files and folders and errors out mid-way with the below error... (7 Replies)
Discussion started by: mohtashims
7 Replies

10. Shell Programming and Scripting

Find command works on Linux but fails on Solaris.

Hi, I am looking for a generic find command that works on both Linux and Solaris. I have the below command that works fine on Linux but fails on solaris.find /web/config -type f '(' -name '*.txt' -or -name '*.xml' -name '*.pro' ')' Fails on SunOS mysolaris 5.10 Generic_150400-61 sun4v sparc... (1 Reply)
Discussion started by: mohtashims
1 Replies
TESTS(7)					       BSD Miscellaneous Information Manual						  TESTS(7)

NAME
tests -- introduction to the NetBSD test suite DESCRIPTION
The NetBSD test suite provides a collection of automated tests for two major purposes. On the one hand, the test suite aids developers in catching bugs and regressions in the code when they performing modifications to the source tree. On the other hand, the test suite allows end users (and, in particular, system administrators) to verify that fresh installations of the NetBSD operating system behave correctly in their hardware platform and also to ensure that the system does not suffer from regressions during regular system operation and maintenance. The NetBSD tests are implemented using the Automated Testing Framework (ATF), a third-party package shipped with NetBSD; see atf(7) for details. The NetBSD test suite is distributed as a separate installation set, named tests.tgz, and the test programs are all installed under the /usr/tests hierarchy. This manual page describes how to execute the test suite and how to configure some of its optional features. When to run the tests? Before diving into the details of how to run the test suite, here are some scenarios in which you should be running them: o After a fresh installation of NetBSD to ensure that the system works correctly on your hardware platform. o After an upgrade of NetBSD to a different version to ensure that the new code works well on your hardware platform and that the upgrade did not introduce regressions in your configuration. o After performing changes to the source tree to catch any bugs and/or regressions introduced by the modifications. o Periodically, maybe from a cron(8) job, to ensure that any changes to the system (such as the installation of third-party packages or manual modifications to configuration files) do not introduce unexpected failures. Installing the tests If you chose to install the tests.tgz distribution set while setting up your NetBSD system, the tests are already available in /usr/tests. Otherwise, install the set now by running: # cd / # tar xzpf /path/to/tests.tgz Running the tests Use the following commands to run the whole test suite: $ cd /usr/tests $ atf-run | atf-report The above will go through all test programs in /usr/tests recursively, execute them, and, at the very end, show a report of the results of the test suite. These results include the count of tests that succeeded (passed), the names of the tests that failed, and the count of the tests that were not executed (skipped) because the system configuration did not meet their requirements. If you are interested in saving the whole output of the test suite execution so that you can later investigate failures, use the following idiom instead: $ cd /usr/tests $ atf-run | tee ~/tests.log | atf-report The above command will save the raw output of the test suite in ~/tests.log, which you can later inspect manually to look for failures. Note that the file contains a copy of the 'stdout' and 'stderr' of each test case, which becomes valuable during debugging. It is also possible to restrict which tests to execute so that only a small subsystem is tested; see atf-run(1) for details. Additionally, it is also possible to run the test programs themselves by hand; see atf-test-program(1) for more details, but be aware that you should only be doing this if you are debugging failing tests. Configuring the tests Some test cases in the NetBSD test suite require the administrator to manually set up some configuration properties before they can run. Unless these properties are defined, the tests that require them will be marked as skipped and thus they will not be really executed. Each test suite is configured through a separate file that lives under /etc/atf/ and that carries the name of the test suite. Henceforth, to configure the properties that affect the execution of the NetBSD test suite, you need to edit /etc/atf/NetBSD.conf. The suite-specific con- figuration file implicitly depends on /etc/atf/common.conf, which contains properties shared among all test suites. These files conform to the configuration file format described in atf-formats(5). The following configuration variables are available in the NetBSD test suite: fstype When set to a filesystem type, restrict tests programs from the /usr/tests/fs/vfs/ tree to only run test cases for the given type. unprivileged-user This variable allows setting an unprivileged user login name to be used by tests. Defaults to '_tests'. What to do if something fails? If there is any failure during the execution of the test suite, please considering reporting it to the NetBSD developers so that the failure can be analyzed and fixed. To do so, either send a message to the appropriate mailing list or file a problem report. For more details please refer to: o http://www.netbsd.org/mailinglists/ o http://www.netbsd.org/support/send-pr.html FILES
/etc/atf/NetBSD.conf Configuration file for the NetBSD test suite. /etc/atf/common.conf Configuration file for all test suites. /usr/tests/ Location of the test suites. SEE ALSO
atf(7) HISTORY
The tests manual page first appeared in NetBSD 6.0. The ATF testing framework was first distributed with NetBSD 5.0 and the collection of test programs in /usr/tests has been growing since then. AUTHORS
Julio Merino <jmmv@NetBSD.org> BSD
August 5, 2011 BSD
All times are GMT -4. The time now is 09:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy