Workaround for kylix debugger - Take 3
Paulo Marques
Ok, I found a brown paper bag bug in the stub that was probably making it fail in certain setups.
The new version has just been posted to borland.public.attachments. There is a README file in there with instructions.
I believe that this was the final bug, so it should now work for everybody (famous last words).
Even if you already tried previous versions and it worked for you, the previous versions might still fail under different conditions. This version is much more robust, so please give it a try.
--
Paulo Marques
John Kelly
Works for me. Thanks again.
JohnK
John Kelly
> Paulo Marques wrote:
> Works for me. Thanks again.
>
> JohnK
Sorry this was premature of me. ... and I was confused about what
version worked for me. Here is the result of more careful testing...
ptrace1: Works. (This is the one with the mk script)
ptrace2: Gives the errors that seigfriedn is getting.
ptrace3: Works but causes intermittent freezes on startup.
Hope this helps
JohnK
Paulo Marques
>[...]
> ptrace1: Works. (This is the one with the mk script)
> ptrace2: Gives the errors that seigfriedn is getting.
> ptrace3: Works but causes intermittent freezes on startup.
>
> Hope this helps
It sure does.
I left a DEBUG option in ptrace3 so that we could understand better
what's going on.
To use it:
- uncomment the "#define DEBUG" statement at the top of
ptrace_interposer.c
- compile and copy into appropriate directory
- from the console run "./startdelphi > output.txt"
If it hangs, just press Ctrl-C on the console to kill kylix and send the
content of output.txt (gzip'ed or bzip'ed, preferably) directly to my email.
If it doesn't hang, exit kylix and run again from the console to produce
a fresh new output. If you continue using kylix without exiting and it
hangs, the output file will be so huge, that it will be very hard for me
to find exactly where it went wrong.
By the way, if by "freezes on startup" you mean kylix startup (and not
the application startup) then it is probably something completely different.
During my tests, sometimes, when the debugger gave the nasty error
messages, killing kylix was not enough and a few debugger processes
would still be hanging there consuming 100% cpu time. Starting kylix
during that phase would take a very long time.
--
Paulo Marques
John Kelly
> By the way, if by "freezes on startup" you mean kylix startup (and not
> the application startup) then it is probably something completely
> different.
Yes, the occasional freeze at startup seems to be unrelated to ptrace.
Sorry for any confusion. It's a new install on SuSE 10 and it looks
like a new problem. :-(
JohnK