Inter-SEGMENT Transition Issue, or STACK overflow?

[Guest]

I am working in a project with a 16F876A.
The project is taking a 46% of the ROM (3.68KB out of 8KB).
The thing is that when a new function is added, the program stops working as it should.
This miss-behavior cannot be blamed on the new funcionallity. To be more concise: This new function is outside the “infinite loop” of the program, is a display presentation that is only executed once, and works nice.
After that, the infinite loop is entered and it is there where the behavior goes erratic and garbled.

I thought it had to be with some inter-SEGMENT transition, or some piece of code too large to be located in one segment.
I went through the output files of the compiler to look for something suspicious, but I didn’t.

MAIN = 22% ROM
1 unused SEGMENT
The rest of funcions range from 1% to 14% (mostly 1 to 6%)

In case is of some help to any kind of genius, this is a comparison between the two compilations, first with the added function and second without it:

[Ttelmah]

I'd be looking at the possibility of a _RAM_ problem. What you describe,is 'semi-classic', for something using a pointer/array, and overwriting a variable, that it shouldn't touch, which then results in the part of the program that does use that variable, receiving unexpected values....
Classic things would be 'forgetting' that a string needs space for the terminating character, and only assiging 10 locations for a 10 character string, resulting in the next variable getting overwritten.

Best Wishes

[Guest]

Yes, you are right, that could be happening.
Nevertheless the new function is not adding more than 14 variables.