Add assert to make sure that function refers to compiled code in handles.cc

Previously, there was a bug there, fixed in r5581. But having an assert still makes sense.

Also, add functions registration to CPU profiler in case
when closure code wasn't compiled yet.

Committed: http://code.google.com/p/v8/source/detail?r=5582

[Rico, 2010-10-04 12:27:31]

LGTM

http://codereview.chromium.org/3557007/diff/1/3
File src/handles.cc (right):

http://codereview.chromium.org/3557007/diff/1/3#newcode813
src/handles.cc:813: PROFILE(FunctionCreateEvent(*function));
Maybee assert that the code on the function object is not the compile stub
(since this would have caught the old bug) and the same above in CompileLazy

[mnaganov (inactive), 2010-10-04 12:37:58]

http://codereview.chromium.org/3557007/diff/1/3
File src/handles.cc (right):

http://codereview.chromium.org/3557007/diff/1/3#newcode813
src/handles.cc:813: PROFILE(FunctionCreateEvent(*function));
On 2010/10/04 12:27:31, Rico wrote:
> Maybee assert that the code on the function object is not the compile stub
> (since this would have caught the old bug) and the same above in CompileLazy

OK, added!