Answer:
I get 0x55 and this the linking address of the main function.
use this function to see changes:
/* bar6.c */
#include <stdio.h>
char main1;
void p2()
{
printf("0x%X\n", main1);
}
Output is probably 0x0
you can use your original bar6.c with updaated foo.c
char main;
int main() // error because main is already declared
{
p2();
//printf("Main address is 0x%x\n",main);
return 0;
}
Will give u an error
again
int main()
{
char ch = main;
p2(); //some value
printf("Main address is 0x%x\n",main); //some 8 digit number not what printed in p2()
printf("Char value is 0x%x\n",ch); //last two digit of previous line output
return 0;
}
So the pain in P2() gets the linking address of the main function and it is different from address of the function main.
Now char main (uninitialized) in another compilation unit fools the compiler by memory-mapping a function pointer on a char directly, without any conversion: that's undefined behavior. Try char main=12; you'll get a multiply defined symbol main...
Explanation:
"detection" by checking for possible cycles or knots.
Answer:
In this case, it seems to me as the system is overheating.
Explanation:
The reason why this is the case is because the processor (CPU) needs airflow to constantly cool itself when running tasks. The airflow works by intakes and exhaust fans within the computer case. Specifically around the processor fan and the heat sink, it is usually designed for exhaust (Some can also be intakes as well). The dust that is collected restricts the fan from properly exhaust all the hot air from the CPU as the dust can be clumped up together. Both the heat sink and the fan are the main components as the air flows through those areas.
Your computer doesn't necessarily just let it burn itself out. It is constantly monitoring the temperatures of the system and if it reaches a limit, it will turn off the system to prevent it from overheating and will turn back on when the temperatures are acceptable to run again.
Have a nice day!
