BlackBox Component Builder Forums

Star button at GitHub.

I published my executable analyze and disassemble framework internally called "PE Decoder" (because Windows PE executables was implemented first). It supports following executable formats: NE (executable format of 16 bit Windows) PE (executable format in modern Windows and UEFI) ELF (UNIX-...

Something like this should be generated by compiler to solve issue (code is functional): MODULE A; IMPORT S := SYSTEM, W := WinApi, COM, Log := StdLog; CONST ExceptionContinueExecution = 0; ExceptionContinueSearch = 1; ExceptionNestedException = 2; ExceptionCollidedUnwind = 3; EXCEPTION_UNWINDING = ...

Test code: MODULE A; IMPORT COM, Log := StdLog; TYPE Object = POINTER TO RECORD (COM.IUnknown) END; PROCEDURE (o: Object) RELEASE; BEGIN Log.String("Object.RELEASE"); Log.Ln; END RELEASE; PROCEDURE (o: Object) FINALIZE; BEGIN Log.String("Object.FINALIZE"); Log.Ln; END FINALIZE; P...

As I remember, Peter Kushnir made analysis for compatibility of BlackBox with Qt several years ago. So he said, that this will not have positive outcome, because Qt works like framework with hidden internal loop with it's own garbage collector etc. And there is no access to lowlevel Qt framework me...

For such cases, I envision Herschel backend will provide additional fixup information at the request of the binder. Probably something like: Code segment for 64 bit modules do not contains relocation chains and can be directly executed if proxy segment is not moved. So we can change link address me...

adimetrius wrote:Edit: Have done, added ChartViews.

Last commit is still 7 days ago. "ChartViews" is not found in repository. Have you done "git push"?

First, the OCF format is great - I like it much better than the ELF, had to study both in the last 5 weeks. Second, While we can preserve the overall OCF file structure, some things in it will still have to change. The reason is that OCF holds the image for the metadata, and that hold pointers, and ...

Can someone explain 64 bit OCF use block format? It's format is incompatible with regular fixups. Also why first empty record is needed in proxy block?

It will be nice to have 64 bit OCF documentation.

Proposed fix is confirmed A.Do [00000057H] .p ARRAY 16 OF PROCEDURE [0] PROCEDURE A.Proc1 [1] PROCEDURE A.Proc2 [2] PROCEDURE A.Proc3 [3] PROCEDURE NIL [4] PROCEDURE NIL [5] PROCEDURE NIL [6] PROCEDURE NIL [7] PROCEDURE NIL [8] PROCEDURE NIL [9] PROCEDURE NIL [10] PROCEDURE NIL [11] PROCEDURE NIL [1...