Welcome, Guest. Please login or register.

Author Topic: Ctrl-C handling issues  (Read 7497 times)

Description:

0 Members and 4 Guests are viewing this topic.

Offline lsmart

  • Sr. Member
  • ****
  • Join Date: Jun 2009
  • Posts: 433
    • Show all replies
Re: Ctrl-C handling issues
« on: June 11, 2011, 04:28:55 PM »
I am sure I can“t help you, but maybe you find the souliton if you ask yourself some smart questions like:
* Does your program have multiple tasks?
* Is it started from Workbench, or is the break signal sent via CLI?

Seeing the string look identical is nice, but have you patched your code or used a debugger to ensure it is really read from that memory location?
 

Offline lsmart

  • Sr. Member
  • ****
  • Join Date: Jun 2009
  • Posts: 433
    • Show all replies
Re: Ctrl-C handling issues
« Reply #1 on: June 11, 2011, 04:37:28 PM »
One more:

* are all your units of compilation (i.e. before linking) share the same definitions of chkabort and CXBRK?
 

Offline lsmart

  • Sr. Member
  • ****
  • Join Date: Jun 2009
  • Posts: 433
    • Show all replies
Re: Ctrl-C handling issues
« Reply #2 on: June 13, 2011, 07:42:30 AM »
Quote from: Minuous;644249
>it auto-opens the CLI window on its first printf().

You are using printf? Doesn't this mean you are including and linking some standard C-Library stuff, which might include its own definitions for handling BRK? Are you using your own startup code?

Maybe ChaosLord is right. Try it on a "virgin Workbench". How often does the problem occur? You could write a small program/loop that does nothing but start AA (or better a third small programm that just shows the CTRL-C problem) and then send BRK .