12-13-2010
Also, when you cannot write to the current directory, no core is written. Does your program call chdir()? Try looking there as well.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Dummies Questions & Answers
I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start
but savecore failed to create the two files, that is vmcore.n and vmunix.n.
savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname
1)... (4 Replies)
Discussion started by: hassan2
4 Replies
3. Programming
MY friends:
my program under sco unix have a problem?
it create a core dump file on the path when execute program ,
but i can't find the error of the C program ,i don't know how to
see the error about my program use core, please help me
or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies
4. UNIX for Advanced & Expert Users
Hi All,
i am new to this forum.i want detail of reading the core file and trace the problem because of what the program get crashed.please help me.if any body knows any website or tutoril plese let me know.
sudhir (6 Replies)
Discussion started by: sudhir patnaik
6 Replies
5. UNIX for Dummies Questions & Answers
Hi All
I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
Discussion started by: gyanusoni
0 Replies
6. AIX
My application gives core dump. When i am debugging with dbx getting instructions below:
pthdb_session.c, 818: 695445 PTHDB_INTERNAL (internal error)
pthreaded.c, 1941: PTHDB_INTERNAL (internal error)
Illegal instruction (illegal opcode) in . at 0x0
warning: Unable to access address 0x0... (1 Reply)
Discussion started by: bapi
1 Replies
7. Programming
how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies
8. AIX
Hi ,
I want to read core dump file on AIX5.3. While i am trying to use following commands, i am getting only few lines of information.
ux201p3:e46123> dbx capsWrkstnMgr core
Type 'help' for help.
reading symbolic information ...
Segmentation fault in malloc_common.extend_brk at... (1 Reply)
Discussion started by: rps
1 Replies
9. HP-UX
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Discussion started by: messi777
1 Replies
10. Solaris
Hi guys,
just want to know which core file pattern is best to set for core dumps:
1) per-process file name pattern
or
2) global file name pattern.
I will really appreciate an explanation why the chosen one is better.
Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 Replies
chdir(2) System Calls Manual chdir(2)
NAME
chdir, fchdir - Changes the current directory
SYNOPSIS
#include <unistd.h>
int chdir ( const char *path );
int fchdir ( int filedes );
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
chdir(): XSH5.0
fchdir(): XSH5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
PARAMETERS
Points to the pathname of the directory. Specifies the file descriptor of the directory.
DESCRIPTION
The chdir() function changes the current directory to the directory indicated by the path parameter.
The fchdir() function changes the current directory to the directory indicated by the filedes parameter. If the path parameter refers to a
symbolic link, thechdir() function sets the current directory to the directory pointed to by the symbolic link.
The current directory, also called the current working directory, is the starting point of searches for pathnames that do not begin with a
/ (slash). In order for a directory to become the current directory, the calling process must have search access to the directory.
NOTES
The current working directory is shared between all threads within the same process. Therefore, one thread using the chdir() or fchdir()
functions will affect every other thread in that process.
RETURN VALUES
Upon successful completion, the chdir() function returns a value of 0 (zero). Otherwise, a value of -1 is returned and errno is set to
indicate the error.
ERRORS
If the chdir() function fails, the current directory remains unchanged and errno may be set to one of the following values: Search access
is denied for any component of the pathname. The path parameter points outside the process's allocated address space. An I/O error
occurred while reading from or writing to the file system. Too many symbolic links were encountered in translating the pathname. The
length of the path argument exceeds PATH_MAX or a pathname component is longer than NAME_MAX.
Pathname resolution of a symbolic link produced an intermediate result whose length exceeds PATH_MAX. The named directory does not
exist, or is an empty string. A component of the path prefix is not a directory.
If the fchdir() function fails, the current directory remains unchanged and errno may be set to one of the following values: The filedes
parameter is not a valid open file descriptor. The file descriptor does not reference a directory.
RELATED INFORMATION
Functions: chroot(2)
Commands: cd(1)
Standards: standards(5) delim off
chdir(2)