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

long params

I'm having some bizarre behavior with functions that take multiple long values as parameters. If I change them to ints, all is fine, but if they are longs the target locks up on the function call. The simulator also shows "extra" hex addresses on the call stack, but is "normal" when the params are ints.

I simply have a main() routine that calls the following function:

unsigned char *GetBuffer(long, long, long, long);

I.E. b=GetBuffer(0, 320, 240, 1);

Am I missing something obvious?
The target is a 80C390, but I'm not
running in contiguous mode (yet), just in the large memory model.

I just updated to v6.22. (But I had not tried this with v6.21)

Parents
  • I'm new to uV2, but the call
    stack window shows things like
    this for the problematic function:

    000:\EPSON\EGDBUFFERGET \BLINKY\MAIN\129
    001:C:0x0029C3 \BLINKY\MAIN\129
    002:C:0x0029C3 \BLINKY\MAIN\129
    003:C:0x0029C3 \BLINKY\MAIN\129
    004:\BLINKY\MAIN C:0x000000

    Another odd thing to note is that I can't use F11 to step into this "bad" function, I must must select Debug->Step via the menu.

    Kevin

Reply
  • I'm new to uV2, but the call
    stack window shows things like
    this for the problematic function:

    000:\EPSON\EGDBUFFERGET \BLINKY\MAIN\129
    001:C:0x0029C3 \BLINKY\MAIN\129
    002:C:0x0029C3 \BLINKY\MAIN\129
    003:C:0x0029C3 \BLINKY\MAIN\129
    004:\BLINKY\MAIN C:0x000000

    Another odd thing to note is that I can't use F11 to step into this "bad" function, I must must select Debug->Step via the menu.

    Kevin

Children
No data