Page 1 of 1

Cannot create the file with the internal debugger

Posted: Fri Jan 17, 2025 2:24 pm
by Rudy M
Hello,

after installation of PB version 612 I can not run anymore pb files with the "open console" statement.
The problem is on my HP-laptop and on my Lenovo ThinkCentre PC (both with Linux Mint 22 and Xfce as desktop).

I did already everything I saw on this forum to get it working but nothing helps.

All pb files without the use of "openconsole" are running perfect.

Are is there a possibility to reset the PB preferences?

Rudy M

Re: Cannot create the file with the internal debugger

Posted: Fri Jan 17, 2025 4:33 pm
by mk-soft
Maybe forgotten ...

Have you also set under compiler option -> executable format -> console?

Re: Cannot create the file with the internal debugger

Posted: Fri Jan 17, 2025 4:46 pm
by Rudy M
Yess, I put it on "console"
Very strange, before the update I did not had this problem.
I have used this install-file: PureBasic_Linux3_X64_LTS_6.12_wmtw4e.tgz

Re: Cannot create the file with the internal debugger

Posted: Sat Jan 18, 2025 10:35 am
by Rudy M
I did a new test: I used the old V611 pref. file (after replacing 'v611' by 'v612')

but I obtain the same error message.

Re: Cannot create the file with the internal debugger

Posted: Sat Jan 18, 2025 1:14 pm
by mk-soft
For Linux Mint 22 you probably still have to take the PB version Linux2 ...

Re: Cannot create the file with the internal debugger

Posted: Sat Jan 18, 2025 5:23 pm
by Rudy M
I did an installation with x86 version but that didn't work at all.

So I did a full new installation with the x64 version.
3D example "bridge".....................: OK
array example.................................: OK
example with "debug" as output: OK
example with openconsole.........: Does not work "with internal debugger".
2e test (debugger unchecked) ...: Does not work either.

So I still have the problem with "open console" in my programs with the error message "cannot execute with internal debugger.
Please try the stand alone one."

(I did not a test with the previous 6.11 version, so I can not say its a version problem).