• Core Overcharged Mac Os Update
• Mac Os Versions

Apple MacBook Pro MD101HN/A Ultrabook (Core i5 3rd Gen/4 GB/500 GB/MAC OS X Mavericks) laptop has a 13.3 Inches (33.78 cm) display for your daily needs. This laptop is powered by Intel Core i5-3210M (3rd Gen) processor, coupled with 4 GB of RAM and has 500 GB HDD storage at this price point. It runs on MAC OS X Mavericks operating system. Apple list a number of ways to generate core dump files in their TN2124 or Mac OS X Debugging Magic. Here's a couple of extracts: Prior to Mac OS X 10.4, you would enable core dumps on a system-wide basis by changing the line 'COREDUMPS=-NO-' in /etc/hostconfig to 'COREDUMPS=-YES-'. Attention to all users, please note this guide and other khronokernel sites will be shutting down on April 16th, 2020. Reason for this is we've decided to move the guides to a dedicated organization to help simplify the hackintosh process and provide a single, trusted source for hackintosh information.

Hello all,

I have an early 2011 Mac Book Pro base model, no Extra GPU, i7 at 2.0GHz.

My CPU is stuck at 800MHz when ice cold at boot up, and also under load when running a benchmark test.

I got this Mac Book Pro used, and would like to fix this issue.

I am running Linux Mint and using i7z to verify my clock speed.

I am also running Phoronix Test Suite to try an get my clock speed to ever leave 800mhz.

Core temps are running between 51 to 65.

Any ideas? Thanks.

I have tried holding down the left shift, control, and alt keys, while hitting the power button to reset from CPU overcharge.

Then I powered on the PC as normal.

Still locked hard at 800MHz.

I want to see this puppy run at full speed!! 🙂

MacBook Pro, Other OS

Posted on Mar 11, 2015 2:26 PM

Core Overcharged Mac Os Update

If you add 'limit coredumpsize 0' into your ~/.tcshrc or ~/.cshrc file, it should eliminate those files

If you want to have the core files for debug purposes, I'd rather delete them with this command in the crontab:
/usr/bin/find -name /cores/core.* -ctime 1 -delete
This only deletes core files older than 24 hours.

Um, either you or some other program must have turned that on. Apple's default is for core dumps to be limited to 0 bytes, which means you should have none. What were the dumps for?

I'm the author of this 'hint'. I have no idea on what these were for. Have you an idea on how to turn this feature off? I don't remember having turned it on any time, but i try many utilities, so i might have done that by accident. It happened again, though since i deleted that gigabyte.

Ya, I didn't have any at all, and I do recall reading or seeing somewhere that cores were supposed to be eliminated by default with the OS install. I'm not sure how they would get turned on by accident, but on two machines I found none at all.

I found nothing in my cores directory. Seems to be empty. I'll take that as a good sign, although I'm always looking for ways to gain more HD space...

You can check your current limits with the 'ulimit -a' command in bash (type 'help ulimit' for more info) or the 'limit' command in tcsh.
The core should be zero. I did some basic hunting and didn't find any obvious setting in /etc, although you could also check the files /etc/csh.* or /etc/profile* and /etc/bashrc to see if there is a limit command in there that something or someone put in.

The place to look for is in /etc/rc.common, at the end of the file, here's the relevant snip :
# Enable coredumps if requested.
##
if [ '${COREDUMPS:=-NO-}' = '-YES-' ]; then
ulimit -c unlimited
fi
To make sure there is nothing wrong with your defaults you should grep all files involved in startup (etc/rc*, StartUpItems...) for ulimit.
My /cores directory was completely empty and I like it that way :-)

Wow, I don't know how this escaped my 'grepping' :)
Anyway, just to complete the thought for those that don't like tinkering that much, placing this line in your /etc/hostconfig file will **enable** core dumps:
COREDUMPS=-YES-
Make sure it's either not there (the default) or is set to -NO- if you don't want them.

One file, hidden (named with . previous to characters) and less than 4K in size. Good spot to watch, and investigate for missing space, but not applicable here.
Personally, my big drive-eater is all the legacy apps and OS versions I've been maintaining on my system until recently. Three partitions on my OEM drive ate up 10 GB of space for old proggies and systems. I've recently used Carbon Copy Cloner to clone those to disc images on my new Maxtor (for back-up purposes, in case I actually need something) and re-formatted the whole thing.
<sarcasm>That gave me lots of space back.</sarcasm>
<brag>Now I honestly don't know what I'm going to do with the 30 GB of space free on my OEM drive. I've got that in addition to ~40 GB free space on my new Maxtor, and am sure I'll fill it up soon but *hate* to think of that much junk. And it's always junk.</brag>

'In my case, about 30 files of weights ranging from 30 to 70Mb were present.'
Thirty core files? Bud, you've got some significant issues.
Kinda reminds me of Nero fiddling while Rome burned.
--Richard

I found my cores file empy, but I found another hidden file
at /private/cores... what is this file for?
It has two files in it called 'cores.199' and 'cores.200' date from 5/2002 and 6/2002.
BF

Well, I found 30 some files at 2.42 Gb. For some reason, removing them restored slightly over 3 Gb to my system.
This is something I'll be keeping an eye on in the future.

Mac Os Versions

Hi:
Just came across your post about core files. I'm learning about them as well in my Unix book for OS 10 by Dave Taylor. I did a find for all my core files and found these:
/Applications/.metadata/.plugins/org.eclipse.debug.core
/Applications/.metadata/.plugins/org.eclipse.jdt.core
/Applications/.metadata/.plugins/org.eclipse.pde.core
/Applications/eclipse/p2/org.eclipse.equinox.p2.core
/Users/chrislandalusa/Documents/workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/Chapter03_Listing01/org.eclipse.jdt.core
/Users/chrislandalusa/Documents/workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/first project/org.eclipse.jdt.core
/Users/chrislandalusa/Documents/workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/ShowAFrame.java/org.eclipse.jdt.core
/Users/chrislandalusa/Documents/workspace/.metadata/.plugins/org.eclipse.debug.core
/Users/chrislandalusa/Documents/workspace/.metadata/.plugins/org.eclipse.jdt.core
/Users/chrislandalusa/Documents/workspace/.metadata/.plugins/org.eclipse.mylyn.bugzilla.core
/Users/chrislandalusa/Documents/workspace/.metadata/.plugins/org.eclipse.team.cvs.core
/Volumes/WINDOWS/Documents and Settings/Chris/.metadata/.plugins/org.eclipse.jdt.core
/Volumes/WINDOWS/Documents and Settings/Chris/.metadata/.plugins/org.eclipse.debug.core
I don't think, given the locations, that theses are core files from a crashed program (unless I'm reading them wrong). Are they? or are they files for my eclipse application that also have a .core extension?
I went to the /core folder on my mac and found nothing there.