10-29-2010
cwd means Current Working Directory.
If the process owner cannot write to that directory there will be no "core" file.
This also applies if the cwd does not exist (yes it can happen).
Did you write the program?
Does it fail immediately or on some condition?
Maybe this post from a Fedora forum is relevant.
http://forums.fedoraforum.org/showthread.php?t=237200
Last edited by methyl; 10-29-2010 at 11:54 AM..
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. UNIX for Dummies Questions & Answers
Hi All,
is there any way to find out the optimal/would be size of the cor dump file generated by the system while a process got terminated abnormally?
Basically we have been asked to provide the size of the core dump file being generated by the administrators who maintained the UNIX boxes.... (4 Replies)
Discussion started by: pushp.gahlot
4 Replies
4. Programming
by what name does a core dump file stored???
like i wrote a test code:
//dump.c
main()
{
char *p=NULL;
printf("%s",p);
}
of course the above code will produce a segmentation fault. but i cant see any file named core in my CWD. am using SUN0S 5.9 (6 Replies)
Discussion started by: vikashtulsiyan
6 Replies
5. 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
6. Programming
Hi All,
May be it is a stupid question, but, I would like to know what is the advantage using a core dump file at the moment of debugging using gdb.
I know a core dump has information about the state of the application when it crashed, but, what is the difference between debugging using the... (2 Replies)
Discussion started by: lagigliaivan
2 Replies
7. 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
8. Emergency UNIX and Linux Support
Hi,
I have got core dump stating "core.bash.29846" so i am unable to open.
How to open the core dump file for further analysis?
Reagards
Vanitha (7 Replies)
Discussion started by: vanitham
7 Replies
9. 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
10. Solaris
I am new to UNIX.
My Application is using c (.so files) and Java code.
My application crashes and CORE DUMP file is generated ,which is huge.
Now I want to view the CORE DUMP file to debug the application using dbx without starting process again.
By only using the CORE DUMP file and dbx ,can i... (1 Reply)
Discussion started by: satde
1 Replies
LEARN ABOUT DEBIAN
debpear
debpear(1) General Commands Manual debpear(1)
NAME
debpear - automatically builds and installs PEAR packages as Debian packages
SYNOPSIS
debpear [options] <pear-package-name>
DESCRIPTION
debpear is a tool to automatically create and build a Debian package out of a PHP PEAR package. It will download the PEAR package from
pear.php.net, then by looking into it, create the corresponding Debian package, and eventually also installs it.
PARAMETERS
<pear-package-name>
Defines the PEAR package name you want to install, as seen on the http://pear.php.net/ site. Make sure respect the case in the name
of the package (for example: Package_NAME).
OPTIONS
--build-dir|-b
Specify the directory where the Debian package will be built.
--verbose|-v
Makes debpear more verbose.
--channel|-c channel
Specify the URL channel of the PEAR package. Currently not implemented: please contribute!
--tarball|-t tarball --pkg-version|-pv pkg-version [ --wget|-w URL ]
Do not use "pear download" to optain the PEAR package from upstream authors. Instead, use tarball and use pkg-version when building
the package. Eventually also download the tarball from URL using wget before building.
--install|-i
Install the resulting debian package in your system. Note that you must be root to use this option. If you aren't root, then debpear
will try to get root using sudo.
EXAMPLE
debpear -i Auth_RADIUS
This will create a php-auth-radius package in ./build-area, and automatically install it. Because it's written in the package.xml
shipped with Auth_RADIUS at pear.php.net, php-auth-radius will depend on php5-radius.
debpear -t current.tgz -pv 1.3.1 -w http://downloads.jasig.org/cas-clients/php/current.tgz CAS
Downloads cas-clients from http://downloads.jasig.org/cas-clients/php/current.tgz, as current.tgz in the current directory, then
builds it as if it was downloaded as CAS-1.3.1.tgz by "pear download".
IMPORTANT
Note that the debian/copyright file generated by debpear isn't good enough for redistribution of the created packages. You should
carefuly review the PEAR package license before doing so. Also, debpear has been created for convenience, but it will never replace
the manual work of an experienced Debian maintainer for creating PEAR packages. It can, however, be used to create a template pack-
age quickly, before a careful review, in order to save time building a Debian PEAR package.
AUTHORS
debpear has been written by Thomas Goirand <zigo@debian.org>, and is maintained inside the PKG PHP PEAR Debian team, that can be
reached at: <pkg-php-pear@lists.alioth.debian.org>.
debpear(1)