jaPBe for PB 3.91 Beta

Karbon · Post by **Karbon** » Wed May 05, 2004 5:56 pm

It is not SQLite... Total mystery as it works every time now..

Craaaaaazy gremlins!

blueznl · Post by **blueznl** » Wed May 05, 2004 7:58 pm

well, karbon, can't help but notice there's only one constant in the equation... you

GPI · Post by **GPI** » Wed May 05, 2004 8:01 pm

El_Choni wrote:Weird thing is that you don't have this problem with the PB IDE, as you say.

The second weird thing is, that i know only two persons with the problem...

The fake-linker only "grabs" command-string from the pbcompiler and give it to the real linker with the additional resources...

And the resources are created with porc, so that can't be the problem.

btw: Can i have a small example-code, which make the problem (and which userlibraries i need to reproduce).

caos.kin@freenet.de

GPI

p.s.: Reinstall doesn't help?

Karbon · Post by **Karbon** » Wed May 05, 2004 8:04 pm

I compiled the problem project once with onError support and handler code - it compiled with no error. After that I took away the OnError support from the compile and commented out the error handling code and since then it's compiled clean every single time. I didn't change anything other than that and kept all the userlibs..

This is the error handling code :

Code: Select all

ErrorInfo:
   
  ErrorNumber.l = GetErrorNumber()
  ErrorDescription.s = GetErrorDescription()
  ErrorModule.s = GetErrorModuleName()
  ErrorLineNumber.l =GetErrorLineNR()
   
  If OpenFile(0, FileName)
    WriteStringN("Error Number: " + Str(ErrorNumber))
    WriteStringN("Module:  " + ErrorModule)
    WriteStringN("Description:  " + ErrorDescription)
    WriteStringN("Line Number:  " + Str(ErrorLineNumber))
    CloseFile(0)
   EndIf
   
   ClearError()

So nothing fancy.. I also checked "enable OnError lines support" in compiler options..

Blue: Like I said on IRC the other day - when in doubt it's almost always user error... I fixed the problem, damned if I don't how though!

Anyway.. GPI, I can't send you any code to reproduce the problem because it only happened with the one project.. All is well now..

GPI · Post by **GPI** » Wed May 05, 2004 9:30 pm

Karbon wrote:Anyway.. GPI, I can't send you any code to reproduce the problem because it only happened with the one project.. All is well now..

It would be nice, when you can reproduce this bug. It is possible that you found a very tricky bug in PB (or in jaPBe; jaPBe creates a extended "header", but nothing really illegal).

It would be very usefull, to search now. Maybe the problem comes back and then you don't found a "workaround".

Karbon · Post by **Karbon** » Wed May 05, 2004 10:13 pm

Just got something a bit crazy...

A window popped up with this in it :

/OUT:"PureBasic73021140.exe" | /ENTRY:start | Start.o | /SUBSYSTEM:Windows | /LIBPATH:"..\PureLibraries\Windows\Libraries" | PureBasic.obj | SystemBase.lib | CRTDLL.lib | KERNEL32.lib | USER32.lib | GDI32.lib | COMDLG32.lib | ADVAPI32.lib | COMCTL32.lib | 1.lib | 2.lib | 3.lib | 4.lib | 5.lib | 6.lib | 7.lib | 8.lib | 9.lib | 10.obj | 11.lib | 12.lib | 13.lib | 14.lib | 15.obj | 15D.obj | 16.obj | 16D.obj | 17.obj | 17D.obj | 18.lib | 19.obj | 20.obj | 21.lib | 22.lib | 23.lib | 24.lib | 25.lib | 26.lib | 27.lib | 28.lib | 29.lib | 30.lib | 31.lib | 32.lib | 33.lib | 34.lib | 35.lib | 36.obj | ..\Debugger\Debugger.obj | KERNEL32.LIB | USER32.LIB | GDI32.LIB | COMCTL32.LIB | JCALG1.LIB | OLEAUT32.LIB | OLE32.LIB | SHELL32.LIB | ADVAPI32.LIB | COMDLG32.LIB | URLMON.LIB | WININET.LIB | |
Before Link
len:674
/OUT:"PureBasic73021140.exe" /ENTRY:start Start.o /SUBSYSTEM:Windows /LIBPATH:"
..\PureLibraries\Windows\Libraries" PureBasic.obj SystemBase.lib CRTDLL.lib KER
NEL32.lib USER32.lib GDI32.lib COMDLG32.lib ADVAPI32.lib COMCTL32.lib 1.lib 2.l
ib 3.lib 4.lib 5.lib 6.lib 7.lib 8.lib 9.lib 10.obj 11.lib 12.lib 13.lib 14.lib
15.obj 15D.obj 16.obj 16D.obj 17.obj 17D.obj 18.lib 19.obj 20.obj 21.lib 22.li
b 23.lib 24.lib 25.lib 26.lib 27.lib 28.lib 29.lib 30.lib 31.lib 32.lib 33.lib
34.lib 35.lib 36.obj ..\Debugger\Debugger.obj KERNEL32.LIB USER32.LIB GDI32.LIB
COMCTL32.LIB JCALG1.LIB OLEAUT32.LIB OLE32.LIB SHELL32.LIB ADVAPI32.LIB COMDLG
32.LIB URLMON.LIB WININET.LIB _jaPBe_0.res

and I started getting that damned linker error again!

GPI · Post by **GPI** » Thu May 06, 2004 6:03 pm

Karbon wrote:A window popped up with this in it :

This is a debug-Screen of my fakelinker. Hold shift during compiling and this window will appear.

Maybe something on your system is wrong. Maybe a virus? Maybe not... A german has the same problem and he doesn't found one...

Karbon · Post by **Karbon** » Thu May 06, 2004 6:05 pm

I thought about that too - I've run 3 virus scanners... Crazy..

Karbon · Post by **Karbon** » Thu May 06, 2004 8:33 pm

Just did a total reinstall of jaPBE and PureBasic - it worked for about 15 minutes and 3-4 builds then I started getting the error message again. I spent 3 hours running AdAware, Spybot Search & Destroy, Norton AV, Anti Vir and they all came up empty handed. It's a brand new install of XP Pro with all the available patches..

*sigh*

Karbon · Post by **Karbon** » Thu May 06, 2004 8:39 pm

Icons. Maybe it has something to do with it?

Seems to always succeed when I don't add an icon and only sometimes succeed with one..

GPI · Post by **GPI** » Thu May 06, 2004 9:14 pm

Karbon wrote:Icons. Maybe it has something to do with it?

Seems to always succeed when I don't add an icon and only sometimes succeed with one..

It is possible. Can i have the icon and the complete path of the icon?

Karbon · Post by **Karbon** » Thu May 06, 2004 9:20 pm

Sure..

http://www.ksoftware.net/kbilling.ico

And the path is C:\Documents and Settings\Mitch\Desktop\kbilling\KBilling\kbilling.ico

GPI · Post by **GPI** » Fri May 07, 2004 9:01 pm

Karbon wrote:Sure..

http://www.ksoftware.net/kbilling.ico

And the path is C:\Documents and Settings\Mitch\Desktop\kbilling\KBilling\kbilling.ico

...
No problems here... I think, that i need a code with the error....

Karbon · Post by **Karbon** » Fri May 07, 2004 9:07 pm

I can't send you the full source code, I'm sorry.

jaPBE will work fine for a few compiles and then start displaying the error so try it a few times to make sure..

I will try to write some new code that shows this problem but I've been compiling fine with jaPBE since I stopped using icons!

Num3 · Post by **Num3** » Sat May 08, 2004 10:20 am

Could these problems be, because of the new compiler feature that includes the xp-manifest by default?