09-24-2013
The output of top command for the process daemon shows an increased memory usage from 6 mb the normal usage to 800mb when the daemon is utilized.
After the daemon utilization completes still the memory usage shown is 800 mb and it does not drop down.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi Everybody,
I want to create a shell script named as say "jip" and it is runned.
And i want that when i do ps + grep for the process than this jip should be shown as process.
Infact there might be process with name jip which is already running. (3 Replies)
Discussion started by: shambhu
3 Replies
2. Shell Programming and Scripting
Hello all,
I would be happy if any one could help me with a shell script that would determine all the processes running on a Unix server and post a mail if any of the process is not running or aborted.
Thanks in advance
Regards,
pradeep kulkarni.
:mad: (13 Replies)
Discussion started by: pradeepmacha
13 Replies
3. Programming
I get this Valgrind error while using malloc but if I use calloc then there is no error.
I allocate 8 bytes for the string inside sprintf, 12 for the ip and 1 for the string terminator. This totals 21, so why is it talking about 20 bytes and 18 bytes ?
Partial code:
char ip =... (3 Replies)
Discussion started by: cyler
3 Replies
4. Ubuntu
Hello,
I want to install and run a tool called Daikon on my Ubuntu(latest version)
While compiling I got this error-------->
checking the GLIBC_VERSION version... unsupported version
configure: error: Valgrind requires glibc version 2.2 - 2.11
make: *** Error 1
make: Leaving directory... (3 Replies)
Discussion started by: paramad
3 Replies
5. UNIX for Dummies Questions & Answers
I have been having some trouble trying to get some code working, so I was wondering...what system calls are required to execute a different program from an already running process? (1 Reply)
Discussion started by: Midwest Product
1 Replies
6. UNIX for Dummies Questions & Answers
I have process1 running on one machine and generating some log file. Now another process which can be launched on any machine wants to know if process1 is running or not and also in case it is running it wants to stream the logs file generated by process1 on terminal from which process2 is... (2 Replies)
Discussion started by: saurabhnsit2001
2 Replies
7. BSD
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (0 Replies)
Discussion started by: naveeng
0 Replies
8. UNIX for Advanced & Expert Users
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (1 Reply)
Discussion started by: naveeng
1 Replies
9. UNIX for Advanced & Expert Users
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (6 Replies)
Discussion started by: naveeng
6 Replies
10. Shell Programming and Scripting
Team,
I have multiple batchjobs running in VM, if I do ps -ef |grep java or tomcat I am getting multiple process list.
How do I get my exact tomcat process running and that is unique? via shell script? (4 Replies)
Discussion started by: Ghanshyam Ratho
4 Replies
LLDB(1) BSD General Commands Manual LLDB(1)
NAME
lldb -- The debugger
SYNOPSIS
lldb [-hvdexw] [-a arch] [-l script-language] [-s lldb-commands] [-n process-name] [-p pid] [[--] <PROGRAM-ARG1> <PROGRAM-ARG2> ...]
DESCRIPTION
lldb is the command line interface for the LLDB debugger library. lldb can debug C, C++, Objective-C, and Objective-C++ programs.
The following options are available:
-h, --help
Prints out the usage information for the lldb debugger. The --help text may be more up-to-date and authoritative than the command
line options described in this man page.
-v, --version
Prints out the version number of the lldb debugger.
-a, --arch arch
Specifies which architecture lldb will use when launching the specified program (assuming the provided executable is built for multi-
ple architectures.)
-f, --file filename
Specifies the executable file that will be launching / attaching to.
-n, --attach-name process-name
Specifies the name of a currently-running process to attach to. (or the name of a process to wait for if -w is used.)
-w, --wait-for
When used in concert with -n process-name-E, indicates that lldb should wait for a new process of that name to be started -- and
attach to it as early in the process-launch as possible.
-p, --attach-pid pid
Specifies a currently running process that lldb should attach to.
-l, --script-language language
Tells the debugger to use the specified scripting language for user-defined scripts, rather than the default. Valid scripting lan-
guages that can be specified include Python, Perl, Ruby and Tcl. Currently only the Python extensions have been implemented.
-d, --debug
Tells the debugger to print out extra information for debugging itself.
-s, --source filename
Tells lldb to read in and execute the file "filename", which should contain lldb commands.
-e, --editor
Instructs lldb to open source files using the host's "external editor" mechanism.
-x, --no-lldbinit
Do not automatically parse any '.lldbinit' files.
(If you don't provide -f then the first argument will be the file to be debugged so 'lldb -- <filename> [<ARG1> [<ARG2>]]' also
works. Remember to end the options with "--" if any of your arguments have a "-" in them.)
USING LLDB
In lldb there is a help command which can be used to find descriptions and examples of all lldb commands. To get help on "breakpoint set"
you would type "help breakpoint set".
There is also an apropos command which will search the help text of all commands for a given term -- this is useful for locating a command by
topic. For instance, "apropos breakpoint" will list any command that has the word breakpoint in its help text.
FILES
lldb will read settings/aliases/commands from three files at startup, if they exist.
First, it will read a ~/.lldbinit-debugger command file. If you are using the lldb command line interface, this is ~/.lldbinit-lldb. If you
are using lldb inside a GUI debugger like Xcode this will be ~/.lldbinit-Xcode. This is a useful place to put settings that you want to
apply only when a given lldb command interpreter is used.
Second, ~/.lldbinit is read.
Third, an .lldbinit file in the current working directory (where lldb is started) will be read.
SEE ALSO
The LLDB project page http://lldb.llvm.org/ has many different resources for lldb users -- the gdb/lldb command equivalence page
http://lldb.llvm.org/lldb-gdb.html can be especially helpful for users coming from gdb.
BUGS
To report bugs, please visit http://llvm.org/bugs/
AUTHOR
Maintained by the LLDB Team, http://lldb.llvm.org/
Darwin 7 June, 2012 Darwin