Sometimes when occurs an error in a FPC/Lazarus execution I receive only the hexadecimal address of the interruption. Is this address useful to determine the pascal instruction that causes the execution error? If affirmative, how do I determine the line instruction number?

(I'm still using the -gl directive)

Greetings from Sao Paulo - Brazil

Ricardo

Sometimes when occurs an error in a FPC/Lazarus execution I receive only the hexadecimal address of the interruption. Is this address useful to determine the pascal instruction that causes the execution error? If affirmative, how do I determine the line instruction number?

(I'm still using the -gl directive)

Greetings from Sao Paulo - Brazil

Ricardo

Sometimes when occurs an error in a FPC/Lazarus execution I receive only the hexadecimal address of the interruption. Is this address useful to determine the pascal instruction that causes the execution error? If affirmative, how do I determine the line instruction number?

(I'm still using the -gl directive)

Greetings from Sao Paulo - Brazil

Ricardo

No idea. I would just run the software again using gdb:

gdb meuprograma.exe

break fpc_raiseexception run

Exception

bt

backtrace comes here

Ar? Ricardo Ody wrote

Sometimes when occurs an error in a FPC/Lazarus execution I receive only the hexadecimal address of the interruption. Is this address useful to determine the pascal instruction that causes the execution error? If affirmative, how do I determine the line instruction number?

With objdump (a separate program) this might be useful to determine the routine in which it occurs.

(I'm still using the -gl directive)

If you use -gl, then the line should be shown ?

Michael.

you wrote

With objdump (a separate program) this might be useful to determine the routine in which it occurs.

As I ask, how do I use the hexadecimal address to determine where the problem occurs? (Even using objdump)

> > (I'm still using the -gl directive) If you use -gl, then the line should be shown ?

This is another trouble. This isn't true in most cases. In general I receive only the hexa addr, even using "-gl" directive. I'm using "-gl" by your advice Michael. But I discover that it doesn't give the line numbers in most of cases. Then I think that some another guy can give additional information to aid abnormal end debugging.

Michael.

Ricardo