[newbie] core file ?
Hello, i need the core file generated by the crash of a program, but this core file is not generated... i have ulimit configured to unlimited, the core is no generated... thanks, jose. -- Jose Usoz / Cromosfera http://www.cromosfera.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] core file
Hi Bascule thanks tom, yes i have 96mb ram, it's a bit unnerving to know that file sizes can be lied about/misreported like that, is it just /dev/ entries that do this ? i know this has confused me before, i'm a gui person really and i need to know when to trust what konq is telling me! bascule It's not so much that it's lying. It seems that under Linux, everything is mounted as a file system. My USB is mounted this way, and if theis holds true for memory, then wouldn't it be conceivable that the file would reflect tyhe size of the memory? If I'm wrong, or oversimplifying (a relative newbie myself), then please correct/elabarate. James On Wednesday 03 January 2001 9:30 pm, you wrote: On Wednesday 03 January 2001 02:45 pm, bascule wrote: i have found a file named /dev/core which is approx 95mb (so it is claimed) which points to /proc/kcore also 95mb in size, this confuses me on 2 fronts, how could a symlink be 95mb in size and is this normal, /proc/...being a virtual filesystem - do i need to delete this file or not bascule These aren't really files. Yes, they're vitual, sometimes called pretend files. My /dev/core is 256mb. That's the amount of ram I have. I take it you have 96 ? type 'du -ch /dev/*' (try /proc/* too) and you'll see that most all the 'files' in /dev are -0- byte.The total for the whole /dev directory should only be something over 100k, mostly due to many 1/2k dir listings. Don't delete anything in either /dev or /proc
Re: [newbie] core file
You are not being lied to. All of the files in /proc do not realy exist. This means that until you read them there is nothing there. When you do read them the kernel creats the information that is displayed on the spot. Try cat /proc/meminfo or cat /proc/mounts and the command line to see what I mean. Right now the difference with kcore is that it is a snapshot of your memory at that point. If you type cat /proc/kcore then you will see what is in you memory. Most of it will be crap but some times you will see words from programs that you have run or files that you have saved. That is why knoq reports it as 95mb because if it didn't then you would have no memory. BTW looking at kcore will contuine for ever because the memory is allways been updated. Also writing anything to kcore is a very bad idea. At best it will crash your system. Also I think that the 1mb difference is the memory taken by the kernel, but don't quote me on that. Mark Hillary - Original Message - From: "bascule" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, January 03, 2001 11:57 PM Subject: Re: [newbie] core file thanks tom, yes i have 96mb ram, it's a bit unnerving to know that file sizes can be lied about/misreported like that, is it just /dev/ entries that do this ? i know this has confused me before, i'm a gui person really and i need to know when to trust what konq is telling me! bascule On Wednesday 03 January 2001 9:30 pm, you wrote: On Wednesday 03 January 2001 02:45 pm, bascule wrote: i have found a file named /dev/core which is approx 95mb (so it is claimed) which points to /proc/kcore also 95mb in size, this confuses me on 2 fronts, how could a symlink be 95mb in size and is this normal, /proc/...being a virtual filesystem - do i need to delete this file or not bascule These aren't really files. Yes, they're vitual, sometimes called pretend files. My /dev/core is 256mb. That's the amount of ram I have. I take it you have 96 ? type 'du -ch /dev/*' (try /proc/* too) and you'll see that most all the 'files' in /dev are -0- byte.The total for the whole /dev directory should only be something over 100k, mostly due to many 1/2k dir listings. Don't delete anything in either /dev or /proc
Re: [newbie] core file
On Thu, 4 Jan 2001, Tom Brinkman wrote: Hi Tom, No, Bascule's not asking about core dumps, but about the core device, which definitely shouldn't be deleted. A plain english Ah, oops. My error because of speed. Sorry, I hope Bascule did not follow my advice!! Core dumps can be deleted, but they wouldn't be in either /dev or /proc. This line placed at the end of /etc/bashrc, 'ulimit -c 0' will prevent core dumps from even being written. I noticed that in clean new installs of 7.1 and 7.2 (at least those I know), an entry is made in /etc/profile that core dumps will be prevented as you wrote when the user is not root: # Users generally won't see annoyng core files [ "$UID" = "0" ] ulimit -c 100 Greetings, Paul -- The problem with being unemployed: The moment you wake up, you're on the job. http://nlpagan.net - ICQ 147208 - Registered Linux User 174403 Linux Mandrake 7.2 - Pine 4.31
Re: [newbie] core file
Some time ago read about a way to delet all core file from hard disk when booting or so. Anybody knows how to do it ?. I´m newbie and core file only ocupied some space for me. thanks Daniel On Wed, 3 Jan 2001, bascule wrote: You can delete it. This is generated when (usually as root) you run a Gnome program that crashes. Then a memory dump is generated called 'core'. Paul i have found a file named /dev/core which is approx 95mb (so it is claimed) which points to /proc/kcore also 95mb in size, this confuses me on 2 fronts, how could a symlink be 95mb in size and is this normal, /proc/...being a virtual filesystem - do i need to delete this file or not bascule -- The world is becoming a madhouse. And who does not adjust gets put away. http://nlpagan.net - ICQ 147208 - Registered Linux User 174403 Linux Mandrake 7.2 - Pine 4.31
Re: [newbie] core file
thanks tom, yes i have 96mb ram, it's a bit unnerving to know that file sizes can be lied about/misreported like that, is it just /dev/ entries that do this ? i know this has confused me before, i'm a gui person really and i need to know when to trust what konq is telling me! bascule On Wednesday 03 January 2001 9:30 pm, you wrote: On Wednesday 03 January 2001 02:45 pm, bascule wrote: i have found a file named /dev/core which is approx 95mb (so it is claimed) which points to /proc/kcore also 95mb in size, this confuses me on 2 fronts, how could a symlink be 95mb in size and is this normal, /proc/...being a virtual filesystem - do i need to delete this file or not bascule These aren't really files. Yes, they're vitual, sometimes called pretend files. My /dev/core is 256mb. That's the amount of ram I have. I take it you have 96 ? type 'du -ch /dev/*' (try /proc/* too) and you'll see that most all the 'files' in /dev are -0- byte.The total for the whole /dev directory should only be something over 100k, mostly due to many 1/2k dir listings. Don't delete anything in either /dev or /proc
Re: [newbie] core file
On Wednesday 03 January 2001 05:57 pm, bascule wrote: thanks tom, yes i have 96mb ram, it's a bit unnerving to know that file sizes can be lied about/misreported like that, is it just /dev/ entries that do this ? i know this has confused me before, i'm a gui person really and i need to know when to trust what konq is telling me! You weren't being lied to hehehe You just happened to pick the one device file that connects the kernel and your ram. Use konq to check out some other devices, like hda. It will report -o- bytes. Google 'linux devices' if you want to find out some more about how these pretend files work. Also check out 'linux device registrar' and how come you weren't curious that kong said /dev/core was 95mb when you have 96mb of ram ? Short answer is prob'ly some hardware you've got is grabbin 1mb to use as virtual firmware. Sort'a a win-firmware deal ; -- Tom Brinkman [EMAIL PROTECTED] Galveston Bay On Wednesday 03 January 2001 9:30 pm, you wrote: On Wednesday 03 January 2001 02:45 pm, bascule wrote: i have found a file named /dev/core which is approx 95mb (so it is claimed) which points to /proc/kcore also 95mb in size, this confuses me on 2 fronts, how could a symlink be 95mb in size and is this normal, /proc/...being a virtual filesystem - do i need to delete this file or not bascule These aren't really files. Yes, they're vitual, sometimes called pretend files. My /dev/core is 256mb. That's the amount of ram I have. I take it you have 96 ? type 'du -ch /dev/*' (try /proc/* too) and you'll see that most all the 'files' in /dev are -0- byte.The total for the whole /dev directory should only be something over 100k, mostly due to many 1/2k dir listings. Don't delete anything in either /dev or /proc
Re: [newbie] core file
On Wed, 3 Jan 2001, bascule wrote: You can delete it. This is generated when (usually as root) you run a Gnome program that crashes. Then a memory dump is generated called 'core'. Paul i have found a file named /dev/core which is approx 95mb (so it is claimed) which points to /proc/kcore also 95mb in size, this confuses me on 2 fronts, how could a symlink be 95mb in size and is this normal, /proc/...being a virtual filesystem - do i need to delete this file or not bascule -- The world is becoming a madhouse. And who does not adjust gets put away. http://nlpagan.net - ICQ 147208 - Registered Linux User 174403 Linux Mandrake 7.2 - Pine 4.31
Re: [newbie] core file
On Wednesday 03 January 2001 03:39 pm, Paul wrote: On Wed, 3 Jan 2001, bascule wrote: You can delete it. This is generated when (usually as root) you run a Gnome program that crashes. Then a memory dump is generated called 'core'. Paul No, Bascule's not asking about core dumps, but about the core device, which definitely shouldn't be deleted. A plain english explaination of /dev (and /proc) files is here. http://www.penguinmagazine.com/Magazine/This_Issue/0015 "Unlike ordinary files, device entries are actually pointers to device drivers in the kernel. Each entry has a "major" and "minor" number which correspond to a particular driver. These numbers correspond to a map of devices assigned by the kernel developers. The major number denotes the general class of the device, while the minor number specifies the exact device" Core dumps can be deleted, but they wouldn't be in either /dev or /proc. This line placed at the end of /etc/bashrc, 'ulimit -c 0' will prevent core dumps from even being written. -- Tom Brinkman [EMAIL PROTECTED] Galveston Bay i have found a file named /dev/core which is approx 95mb (so it is claimed) which points to /proc/kcore also 95mb in size, this confuses me on 2 fronts, how could a symlink be 95mb in size and is this normal, /proc/...being a virtual filesystem - do i need to delete this file or not bascule
Re: [newbie] Core file, what is it?
Paul [EMAIL PROTECTED] writes: Indeed. It is a memory dump of a crashed program. This is only (afaik) generated by Gnome-oriented programs. I have once heard of a setting somewhere that prevents these large files from being written, but alas, I have no idea where I left it... something like : ulimit -c 0 in your ~/.bashrc NB: by default on Mandrake it's the default behavior for users and active for the root user. -- MandrakeSoft Inchttp://www.mandrakesoft.com Pittsburg, USA--Chmouel
[newbie] Core file, what is it?
Hi Group, I found in my home directory a rather large size file, which was not there previously, called "core," and the graphic of the file looks like a bomb, with a fuse, no joke. I could not find any info or documentation on this thing. Is it safe to delete? Just exactly what is it. -- Best regards, Gary mailto:[EMAIL PROTECTED] Today's thought: Never argue with a man carrying a water buffalo.
Re: [[newbie] Core file, what is it?]
Gary [EMAIL PROTECTED] wrote: Hi Group, I found in my home directory a rather large size file, which was not there previously, called "core," and the graphic of the file looks like a bomb, with a fuse, no joke. I could not find any info or documentation on this thing. Is it safe to delete? Just exactly what is it. -- Best regards, Gary mailto:[EMAIL PROTECTED] Hi Gary, A "core" file is a file created by a program that has crashed. It is meant to allow someone who knows what they're really doing (I don't ;o) ) to figure out what went wrong. If you don't know what one is, I doubt there's much in there that'll mean much to you. You can just delete it if you'd like. It won't f%$#@ up anything. Mike ~~~ "I'd rather have a bottle in front of me than a frontal lobotomy." --Tom Waits ~~~ Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
Re: [newbie] Core file, what is it?
Den Tue, 06 Jun 2000 skrev du: Hi Group, I found in my home directory a rather large size file, which was not there previously, called "core," and the graphic of the file looks like a bomb, with a fuse, no joke. I could not find any info or documentation on this thing. Is it safe to delete? Just exactly what is it. -- Best regards, Gary mailto:[EMAIL PROTECTED] Today's thought: Never argue with a man carrying a water buffalo. A core file is (If I´m not mistaking) a file leaved by a program when it crashes. Think it´s supposed to be helpfull for programmers trying to find out what happened to the program that crashed. It´s safe to delete it. Typing "file core" will show you which program the file belongs to. /Anders
Re: [newbie] Core file, what is it?
On Tue, 6 Jun 2000, Anders Linden wrote: I found in my home directory a rather large size file, which was not there previously, called "core," and the graphic of the file looks Gary mailto:[EMAIL PROTECTED] A core file is (If I´m not mistaking) a file leaved by a program when it crashes. Think it´s supposed to be helpfull for programmers trying to find out what happened to the program that crashed. Indeed. It is a memory dump of a crashed program. This is only (afaik) generated by Gnome-oriented programs. I have once heard of a setting somewhere that prevents these large files from being written, but alas, I have no idea where I left it... Paul -- Enthusiasm and optimism are the legs of life )0([[EMAIL PROTECTED]])0( http://nlpagan.net - ICQ 147208 Registered Linux User 174403
