This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

unused memory areas are not zero?

Parts of the address area where are not used by the application are not zero (0x00000000)?

e.g. memory areas for CS signals, which were not used?

best regards
Joe

Parents
  • When a development tool (or any other tool for that matter) doesn't do what you expect, there are basically three roads to take:

    1) Complain that something is wrong with the tool.

    2) Ask why the tool behaves as it does.

    3) Spend some time figuring out if the tool behaviour may be meaningful and hence intentional, or if the only reasonable solution is that there is an error in the tool.

    At least 99% of people choosing the #1 road will be wrong. Most errors are misconceptions or user errors.

    #2 may sometimes be a quick way to get an answer, but it is also normally a way that very slowly increases knowledge. The difference between asking and accepting an answer without questioning it, and yourself figuring out a solution is very big. Spending time figuring out solutions means that you get the knowledge to transfer experience directly to future problems. Living on canned answers means that you don't have an idea when the answer is applicable, so whenever you get a new problem, you have to ask new questions.

    Next time something doesn't work as expected, I recommend that you spend some time figuring out a reasonable explanation for the behaviour. Then post the problem and what you think is the reason (including why you think so). You can then improve by comparing your reasoning with the answers from other posters.

Reply
  • When a development tool (or any other tool for that matter) doesn't do what you expect, there are basically three roads to take:

    1) Complain that something is wrong with the tool.

    2) Ask why the tool behaves as it does.

    3) Spend some time figuring out if the tool behaviour may be meaningful and hence intentional, or if the only reasonable solution is that there is an error in the tool.

    At least 99% of people choosing the #1 road will be wrong. Most errors are misconceptions or user errors.

    #2 may sometimes be a quick way to get an answer, but it is also normally a way that very slowly increases knowledge. The difference between asking and accepting an answer without questioning it, and yourself figuring out a solution is very big. Spending time figuring out solutions means that you get the knowledge to transfer experience directly to future problems. Living on canned answers means that you don't have an idea when the answer is applicable, so whenever you get a new problem, you have to ask new questions.

    Next time something doesn't work as expected, I recommend that you spend some time figuring out a reasonable explanation for the behaviour. Then post the problem and what you think is the reason (including why you think so). You can then improve by comparing your reasoning with the answers from other posters.

Children
No data