Problem Loading Library

[Emufr3ak]

Hi Amiga Coders


Trying to use some Math Libraries. The expected result from the test code below would be an endless loop when the library was loaded. This doesn't work however. I get straight back to console.



I'm running this against a vanilla Amiga 1200 Configuration in the Emulator with nothing installed. It's compiled using the Vscode Plugin from Abyss.


If I remove

MathIeeeSingBasBase= (structMathIEEEBase*) OpenLibrary((CONST_STRPTR)"mathieeesingbas.library", 0);
if (!MathIeeeSingBasBase)
Exit(0);


I'm getting the Endless loop. So I believe that's where the code fails.


Any Ideas?



SysBase=*((structExecBase**)4UL);
custom= (structCustom*)0xdff000;

// We will use the graphics library only to locate and restore the system copper list once we are through.
GfxBase= (structGfxBase*)OpenLibrary((CONST_STRPTR)"graphics.library",0);
if (!GfxBase)
Exit(0);

// used for printing
DOSBase= (structDosLibrary*)OpenLibrary((CONST_STRPTR)"dos.library", 0);
if (!DOSBase)
Exit(0);

MathIeeeSingBasBase= (structMathIEEEBase*) OpenLibrary((CONST_STRPTR)"mathieeesingbas.library", 0);
if (!MathIeeeSingBasBase)
Exit(0);



while (TRUE)
{
/* code */
}




CloseLibrary((structLibrary*)DOSBase);
CloseLibrary((structLibrary*)GfxBase);

[a/b]

This is a ROM library, so... here comes a blink kick ><.
It's not opened automatically during boot etc., so maybe out of memory? How much is left after you've started your program?

[Emufr3ak]

This is basically all my program is doing. There's a main loop around it but that's it.

[Minuous]

Does this compiler use 16-bit ints? That would explain the problem if so.

[a/b]

Post exe? I'm not sure what else could go wrong (it's C and not asm, so who knows).
AFAIK load order is memory first, then disk. Thinking about having a disk based library with the same name that requires an FPU and thus fails to load/init. The one in ROM 3.x should handle FPU and no FPU scenario.
Do you have any tool/app that uses that library, and if so does it also fail to start?
In winuae debugger (shift-F12), you can use Tl command to get a list of currently loaded libraries. Does it eventually show up there?

[Emufr3ak]

It's gcc. I think the frameworks using it's own version. I'm not exactly sure where the framework stores the executable for the compiler.

[Emufr3ak]

Just noticed I made a stupid mistake. I changed my example before posting it. The one above worked.

The issue is with mathieeetransbase. Below example immediately returns to shell

int main() {
SysBase = *((struct ExecBase**)4UL);
custom = (struct Custom*)0xdff000;

// We will use the graphics library only to locate and restore the system copper list once we are through.
GfxBase = (struct GfxBase *)OpenLibrary((CONST_STRPTR)"graphics.library",0);
if (!GfxBase)
Exit(0);

// used for printing
DOSBase = (struct DosLibrary*)OpenLibrary((CONST_STRPTR)"dos.library", 0);
if (!DOSBase)
Exit(0);

MathIeeeSingBasBase = (struct MathIEEEBase *) OpenLibrary((CONST_STRPTR)"mathieeesingbas.library", 0);
if (!MathIeeeSingBasBase)
Exit(0);

MathIeeeSingTransBase = (struct MathIEEEBase *) OpenLibrary("mathieeesingtrans.library",37);
if (!MathIeeeSingTransBase)
Exit(0);


while (TRUE)
{
/* code */
}




CloseLibrary((struct Library*)DOSBase);
CloseLibrary((struct Library*)GfxBase);
}

[a/b]

That library is always disk based, so it should be present in LIBS:.

[Emufr3ak]

So mathieeesingtrans.library is disk based. That definitely explains it. As it's part of the OS I can expect it to be there on a HD Based System?

[Thomas Richter]

Note that your resource management is flaky. It is not correct to call exit if opening one of the libraries failed to open. You also need to close all those libraries you could open so far. Mathieeesingtrans is in LIBS: on harddisk-based installations, yes.

[No.3]

Originally Posted by Thomas Richter

Note that your resource management is flaky. It is not correct to call exit if opening one of the libraries failed to open. You also need to close all those libraries you could open so far.

and it would be nice if an (helpful!) error message would be printed...

[Olaf Barthel]

Originally Posted by Thomas Richter

Note that your resource management is flaky. It is not correct to call exit if opening one of the libraries failed to open. You also need to close all those libraries you could open so far. Mathieeesingtrans is in LIBS: on harddisk-based installations, yes.

More to the point, calling Exit() as opposed to exit() will skip the program's cleanup operations. You should never ever call Exit() from a 'C' program because it will end up using the shortest possible path to return control to the shell Process which launched it. No allocated signals will be released and no file handles will be closed.