Software Archive
Read-only legacy content
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17060 Discussions

Disassembling

Intel_C_Intel
Employee
‎08-13-2001 08:20 PM
451 Views
When I try to execute my program, I get a run-time error...
"The instruction at "0x77f6ce4c" referenced at memory at "0x00000010". The memory could not be "written"."

and when the debugger (disassembling window) starts up, it points to this line...
"77F6CE4C inc dword ptr [eax+10h]"

How could I use this reference to pin-point where this error is occuring in my code?
0 Kudos

Link Copied

3 Replies
Steven_L_Intel1
Employee
‎08-13-2001 10:40 PM
451 Views
What is the complete text of the first error message?

Steve
0 Kudos
Copy link
Intel_C_Intel
Employee
‎08-13-2001 11:03 PM
451 Views
That is all it says. Then it just ask whether you want to terminate the program, or to try to debug the error
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎08-14-2001 01:34 AM
451 Views
How did you cause the program to begin execution? Does this happen only in Developer Studio, or any time? If in Developer Studio, did you use the ! (Execute) button or the Go button that starts the debugger? Did you build this as a Debug configuration? What Windows version are you using?

Steve
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.