2 replies to this topic

[TheKingfish]

[FONT=&]I’m back. Still the total newbie to FPC (2.4.4), but now seeking some runtime error help. In attempting to run one of my old Turbo Pascal programs, I’m encountering a snag on FPC. I did not expect any issues with the tried-and-true code. Although a longtime user of TP, I have never fully utilized the tool offerings (monitoring, debugging, etc.). I’ve more or less slugged it out minus any peripheral assistance – the equivalent of the blind pig that eventually finds an acorn……[/FONT]

[FONT=&]Over the years, I’ve often amazed myself in finding my way through the error maze. In the end I’m confident this is more a generic Pascal-programming issue than FPC. Never too old to learn the basics and the existing assist tools I guess. Anyway, here’s what I’m seeing:[/FONT]
[FONT=&]Runtime error 201 at $0041662D (plus three other $ locations)[/FONT]

[FONT=&]By appendix definition this has to do with something being outside of range, but I’m unsure of where to start looking. The dollar-sign location notation is unknown to me. Can anyone shine some additional light my way? Thank you.[/FONT]

[LuthfiHakim]

"Runtime error 201 at $0041662D ..."

this means that code at address $0041662D causing error with code 201. I don't remember what error code 201 is. It could be OS error forwarded by the compiler, Pascal error handling, or the application specific erro code.

You can try to generate map file of your codes and find which line is located at $0041662D (or covering it).

[TheKingfish]

[FONT="]Thanks for your input. The formal search for runtime errors within Pascal (embedded code for identifying the line number) has always seemed to be a cure worse than the disease. But that’s both (1) me and the (2) lack of ever finding a good example.[/FONT]
[FONT="] [/FONT]
[FONT="]For my problem I came to recognize the error was confined to the subroutine I was evoking, as opposed to the entire former Turbo program being processed by FPC. So, I set upon the standard troubleshoot technique – methodically inserting screen-prints to identify the discrepancy location. That device worked well, and I soon had a suspect area cordoned off. Not surprising, the area was something I’d created just last year; a piece of code less-elegant than it could have been. I think we all know when that happens, but the code invariably works in the short term and we are often momentarily reluctant to invest more time. Nonetheless, this week I put the proper time into it and resolved the issue. Always a good feeling. Again, thanks for your help. The forum remains an asset, one that I much appreciate.[/FONT]