I have a vague recollection (from previous discussions on the list) that this sort of problem only occurred if debugging was enabled, or am I thinking of some other problem?
Joe.
-----Original Message----- From: Frank Heckenbach [SMTP:frank@g-n-u.de] Sent: Thursday, November 29, 2001 4:20 AM To: gpc@gnu.de Subject: Re: investigating a core dump...
Stephan Eickschen wrote:
This might be a case of a known GPC problem that causes a stack overflow if the loop runs very often. If it's that, than the crash should occur sooner or later depending on the stack limit set.
A work-around in this case could be to assign the loop condition (substr(zeile2,1,ls)=suchstr) to a Boolean variable and test this in the `until'.
Thanks a lot! The program seems to work now...
Fine. The GPC bug might be fixed in the not too distant future, but I don't want to promise too much.
Frank
-- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html
da Silva, Joe wrote:
I have a vague recollection (from previous discussions on the list) that this sort of problem only occurred if debugging was enabled, or am I thinking of some other problem?
Probably, though I'm not sure which one. The "stack eating" bug is not related to debugging.
Frank
Joe,
I have a vague recollection (from previous discussions on the list) that this sort of problem only occurred if debugging was enabled, or am I thinking of some other problem?
For my - now solved - problem I can state that it first occured without "debugging enabled". Certainly, when the seg fault happened I turned it on until it vanished. Now the program run with and wothout debugging enabled.
Stephan
-
da Silva, Joe -
Frank Heckenbach -
Stephan Eickschen