Differents results debugging between step over and step into

Hello,
The difference in behavior is puzzling. The difference between the two actions is really where the debugger sets the next breakpoint (inside the function itself or after the call) before running. What device are you using and can you provide a test case?

Thanks
ki

I am using a Tiva TM4C123GXL.

The part code involved is:
.......
i2c_write(0x82,0x0A,1);
datorecibido=i2c_read(0x82);
.........
.........
void i2c_write(uint8_t register_address,uint32_t register_data,uint8_t nbytes){
if(nbytes==1){
I2CMasterSlaveAddrSet(I2C1_BASE, 0x0D,false);
I2CMasterDataPut(I2C1_BASE, register_address);
I2CMasterControl(I2C1_BASE,I2C_MASTER_CMD_BURST_SEND_START);
while(I2CMasterBusy(I2C1_BASE)){}
uint8_t register_data1= register_data;
I2CMasterDataPut(I2C1_BASE, register_data1);
I2CMasterControl(I2C1_BASE,I2C_MASTER_CMD_BURST_SEND_FINISH);
while(I2CMasterBusy(I2C1_BASE)){}
}
while(I2CMasterErr(I2C1_BASE) != I2C_MASTER_ERR_NONE){}
return;
}
uint32_t i2c_read(uint8_t register_address){
I2CMasterSlaveAddrSet(I2C1_BASE, 0xD,true);
I2CMasterControl(I2C1_BASE,I2C_MASTER_CMD_SINGLE_RECEIVE);
data = I2CMasterDataGet(I2C1_BASE);
return data;
}
.......

When I debug this clicking on "Step into" or F5 -> datorecibido=0x0A
But clicking on "Step over" or F6 ->datorecibido=0x00

If I click on "Resume" and then "Pause", the program is in a while(1) interrupt :

//This is the code that gets called when the processor receives a fault
// interrupt. This simply enters an infinite loop, preserving the system state
// for examination by a debugger.
//
//*****************************************************************************
static void
FaultISR(void)
{
//
// Enter an infinite loop.
//
while(1)
{
}
}

It's very extrange! Do you know why?

Since this happened, Now I have the program stopped in the first while(I2CMasterBusy(I2C1_BASE)){}

Can you attach a small test case? Basically I am looking for a project + source files that I can build to reproduce the issue.

Thanks
ki

Any new on this? I have the same problem, also with i2c, mine is using Tivaware.