Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Trying to debug truss command of PID in Solaris 10. Post 303032233 by MadeInGermany on Thursday 14th of March 2019 04:26:54 AM
Old 03-14-2019
You say you manually can create files. Did you do this on the Solaris box??
arch/chkpt.arch is relative to the current work directory. Please peek the process with
Code:
pwdx <PID of the running process>

and verify.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Kill a debug command

once I run the debug command for a program, I can't get back to the prompt afterwards. I'm sure there is some escape sequence that will get me back there, but I don't know what it is. Anyone know?--thanks--AJ (3 Replies)
Discussion started by: AJA
3 Replies

2. UNIX for Dummies Questions & Answers

Truss and the FTP command

I have been trying to perform the following command without success truss -feo truss.out ftp -nvd < ftpcmds.txt The error I am getting is "truss: cannot trace set_id or unreadable object file /usr/bin/ftp" I have tested the file that contains the ftp commands and it works fine with ftp... (5 Replies)
Discussion started by: canman
5 Replies

3. Shell Programming and Scripting

what's the debug command for perl scripts

Hi, Can you please let me know if there's any debug command for perl scripts like set -x for shell scripts (2 Replies)
Discussion started by: dayanandra
2 Replies

4. Programming

gdb: how to debug an executable file with a few command line papameters

If an executalbe file has several parameters, gdb can not pass parameters correctly. Let us see: run: ./executablefile1 agr1 arg2 arg3 debug: gdb executablefile1 run executalbefile1 arg1 arg2 arg3 then argv : executablefile1 argv : executablefile argv : arg1 ... (3 Replies)
Discussion started by: cdbug
3 Replies

5. Shell Programming and Scripting

Get Pid from a command output

pariosd -status NodeName ID ROLE STATE PROTECTION --------------------------------------------------------------------------- tn320_scm10 10 ACTIVE UP No Protection tn320_scm11 11 UNKNOWN UNKNOWN LocalApps ... (5 Replies)
Discussion started by: hariprasad123
5 Replies

6. Solaris

Is there a way to debug the startup on Solaris?

Is there a way to debug the startup on a VT100 running Solaris 5? I have a problem related to file attributes that are resetting to there prior settings when the machine reboots. (3 Replies)
Discussion started by: jimcz2it
3 Replies

7. UNIX for Advanced & Expert Users

unable to understand the output of TRUSS command

Hi, I am trying to set ulimit for soft stack unlimited, but this is not taking effect, after tracing the ulimit -a unlimited command, the below output was generated, which i am unable to comprehend. Could any one help me with this? prcbap1-r10prod: truss -d ulimit -s unlimited Tue Dec 30... (2 Replies)
Discussion started by: NasirAbbasi
2 Replies

8. Shell Programming and Scripting

How to get the parent PID only in Solaris?

Hi, I am using this command fuser_result=`fuser -f /web/$1/admin-*/logs/access` to get the parent pid of the process. However, The output differs and at times it shows two pids instead of one thus failing the logic of my script. See output below: bash-3.2$ fuser -f... (3 Replies)
Discussion started by: mohtashims
3 Replies
update_dyld_shared_cache(1)				    BSD General Commands Manual 			       update_dyld_shared_cache(1)

NAME
update_dyld_shared_cache -- Updates dyld's shared cache SYNOPSIS
update_dyld_shared_cache [-root directory] [-overlay directory] [-arch arch] [-force] [-debug] [-sort_by_name] [-universal_boot] [-verify] [-dylib_list file] [-iPhone] [-cache_dir dir] DESCRIPTION
update_dyld_shared_cache ensures that dyld's shared cache is up-to-date. This tool is normally only run by Apple's Installer and Software Update, as they are the only official ways for OS dylibs to be updated. But if for some reason you used another mechanism to alter an OS dylib, you should manually run update_dyld_shared_cache. Note that the new cache does not take effect until the OS is rebooted. If a safe-boot is done (booting with shift key held down) the cache is deleted. The dyld shared cache is mapped by dyld into a process at launch time. Later, when loading any mach-o image, dyld will first check if is in the share cache, and if it is will use that pre-bound version instead of opening, mapping, and binding the original file. This results in significant performance improvements to launch time. update_dyld_shared_cache scans the directory /var/db/dyld/shared_region_roots for text files containing paths to mach-o executables. The full dependencies of all dylibs required by those executables is used to determine which libraries are commonly used and should be placed in the shared cache. If one of the text files contains a path to a dylib, that dylib and its dependents will be forced into the cache. update_dyld_shared_cache builds a separate cache file for each architecture. The cache files and a readable text map of the cached are gen- erated to /var/db/dyld. You must be root to run this tool. The options are as follows: -root directory This option specifies the root of an OS installation for which dyld's shared cache should be updated. This is used by the In- staller to update the dyld shared cache in a partition other than the one you into which you are currently booted. The cache files are created in the var/db/dyld directory of the specified directory. Note: if you are manually doing this, be sure to run the update_dyld_shared_cache tool that is in the partition being updated. This assures the cache format created will match that expected when booting off that partition. -overlay directory This option specifies the root of a sparse directory tree. When building the dyld shared cache, any corresponding mach-o files in the sparse directory will override those in the boot partition. This is used by Software Update to build a dyld shared cache for the update that is about to be installed. The cache files are created in the var/db/dyld directory of the specified direc- tory. -arch arch By default update_dyld_shared_cache generates cache files for all architecture that the current machine can execute. You can override this behavior by specifying one or more -arch options and list exactly which architectures should have their shared caches updated. -force This option will cause update_dyld_shared_cache to regenerated the shared cache files even if they appear to be already up-to- date. -debug This option prints out additional information about the work being done. -sort_by_name By default update_dyld_shared_cache assigns a random start address to each mach-o image in the cache. This option causes the start addresses to be chosen in path order, thus subsequent runs will produce the same address layout which can help reproduce some bugs. -universal_boot This option can only be used running on an machine with an Intel processor. It builds caches that can be used when booting on both 32-bit and 64-bit machines. -dylib_list file Instead of scanning /var/db/dyld/shared_region_roots/, this option provides a file that contains a list of the dylibs to use when building the shared cache file. -verify Will regenerate a shared cache in-memory that matches the randomization of the existing shared cache file. Then instead of writ- ing the cache file, it compares the in-memory cache file to the on disk version and reports any differences. -iPhone indicates that cache is not for the current Mac OS X, but for rather for an iPhone -cache_dir directory This option specifies the directory in which to create the cache file(s). If not specified, the cache file(s) are created in the standard location (e.g. var/db/dyld/) of the root partition. FILES
/var/db/dyld/shared_region_roots directory of text files with paths to mach-o images used to determine what should be in shared cache. SEE ALSO
dyld(1) Darwin Oct 10, 2008 Darwin
All times are GMT -4. The time now is 05:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy