PureBasic Forums - English

Posted: **Sat Aug 13, 2005 12:05 pm**

Fred, since updating to beta 5 my app is coming up with this messagebox
error sometime after I compile and run (ie. not immediately, and it never
appears when I run the compiled exe, which seems to be stable):

Code: Select all

---------------------------
PureBasic Debugger
---------------------------
Connection to debugged executable broken!

Debugger quitting...
---------------------------
OK   
---------------------------

I can't reproduce it, it could be anything... my source is 197 KB and the error
doesn't come up at the same time or place with whatever I'm doing. I just
thought I'd mention it in case it's something simple that you've forgotten.
It doesn't specify any line of code or command so it's hard to isolate.

Posted: **Sat Aug 13, 2005 5:49 pm**

This message means that the pipe used for communication between the
program and the debugger (which is a separate process now) cannot be read.
This should not happen (in theory), and i have also never encountered this myself.

Is it possible that i can get that sourcecode ?
If not, i could create some special ide/debugger builds with a few things disabled to help narrow down the problem.

Posted: **Sat Aug 13, 2005 6:20 pm**

I got the message once too, though I didn't know it fell into the "this will never happen" category. If I get it again I'll save everything and post it.

Posted: **Sun Aug 14, 2005 1:29 am**

> Is it possible that i can get that sourcecode ?

Unfortunately not, I'm not an open-source fan and this is my prime app with
a lot of things that I wish to keep under wraps until release. I'm not saying
you would distribute it -- I trust you 100% -- but I just don't want anyone
to see what I'm doing, that's all.

(In comparison, it'd be like me asking
to get hold of the entire PureBasic source for a look at it).

> If not, i could create some special ide/debugger builds with a few things
> disabled to help narrow down the problem.

Don't bother. It's not something that occurs all the time. If it's any help,
I think it may be something to do with deleting items from a ListIconGadget.
I deleted all items and the error occurred immediately at one time, but not
with the same ListIconGadget ever since... so I don't know. I'll keep a good
watch from now and try to observe how/when it happens so that I can try to
make a small standalone reproducable snippet.

Also, I do kill my app with the "Kill" button on the Taskbar, perhaps that
is doing something to the processes? Eg. kill then compile/run, repeat.

Posted: **Sun Aug 14, 2005 3:03 pm**

The problem appears to be the fact that the beta5 creates the debugged process with the debug flag.
It seems to cause trouble like this for quite a few people, so we will remove
that for the final release again. (maybe add it again in the future, if we figured out what is wrong there)

So this should be ok.