Forums - All Posts - The Amigans website

Forum Index

Board index » All Posts (salass00)

Bottom

(1) 2 3 4 ... 88 »

salass00

Re: getcwd() issue or bad usage ?

Posted on: 5/6 9:41 #1

Just can't stay away

@sTix

Actually there is a difference between newlib and clib2 getcwd() in that newlib getcwd() will return the AmigaOS style path if __translate_amiga_to_unix_path_name() fails whereas clib2 will just return an error. Still doesn't explain why it works when the buffer size is 1024.

Topic | Forum

salass00

Re: getcwd() issue or bad usage ?

Posted on: 5/6 8:27 #2

Just can't stay away

@sTix

Newlib uses the same path translation so I doubt it. It just means that if you have the unix path semantics enabled (-lunix) there is little to no benefit from using a buffer larger than PATH_MAX bytes.

Topic | Forum

salass00

Re: getcwd() issue or bad usage ?

Posted on: 5/5 20:11 #3

Just can't stay away

@kas1e

AFAICT there should be no upper limit on the buffer size for getcwd() in clib2 (I looked at the code both for Olaf Barthel's and afxgroup's clib2).

What is errno set to after getcwd() has returned?

Topic | Forum

salass00

Re: A new editor for AmigaOS 4 is in the works

Posted on: 5/3 12:03 #4

Just can't stay away

@trgswe

A more verbose method that should produce the same result:


struct Locale *locale;

ULONG charset = 0;



locale = ILocale->OpenLocale(NULL); /* Get default locale */

if (locale != NULL)

{

    charset = locale->loc_CodeSet;



    ILocale->CloseLocale(locale);

}



/* Locale autodoc says to treat zero as ISO-8859-1 */

if (charset == 0)

{

    charset = 4;

}

BTW the warning note in the GetDiskFontCtrl() autodoc is mainly for the tag pairs like DFCTRL_XDPI/DFCTRL_YDPI or DFCTRL_XDOTP/DFCTRL_YDOTP where you might get a new value for the X and an old value Y if you read them while they are being modified.

Topic | Forum

salass00

Re: A new editor for AmigaOS 4 is in the works

Posted on: 5/3 6:56 #5

Just can't stay away

@LiveForIt

Quote:

it crashes on PowerPC "BLR" opcode, its like the 680x0 "RTS", so my guess is corrupted stack, maybe it has run out of stack.

If that was the case it would be an ISI and not an alert.

In this case what seems to have happened is that the newlib.library dlmalloc allocator has detected an error and posted the alert 0x81000009 (AT_DeadEnd|AN_FreeTwice).

It could be that a bad memory pointer was passed to free() or maybe the memory was already freed before as suggested by the alert code. It is also possible that the magic field in the memory chunk header has been overwritten by a buffer overflow or random memory trashing.

Topic | Forum

salass00

Re: A new editor for AmigaOS 4 is in the works

Posted on: 5/3 6:34 #6

Just can't stay away

@walkero

You don't need unlibdev or other external dependencies to convert between local charset and unicode.

Just use IDiskfont->GetDiskFontCtrl(DFCTRL_CHARSET) to get the IANA number and you can then use IDiskfont->ObtainCharsetInfo() to request a mapping table.


ULONG charset;

const ULONG *maptable;



charset = IDiskfont->GetDiskFontCtrl(DFCTRL_CHARSET);

maptable = (const ULONG *)IDiskfont->ObtainCharsetInfo(DFCS_NUMBER, charset, DFCS_MAPTABLE);

The mapping table is an array of 256 ULONGs that are the unicode (UCS4) equivalents to each character in the local (8-bit) charset.

You can then use this to convert to unicode just like so:


n = IKeymap->MapRawKey(ie, &vanilla, 1, NULL);

if (n == 1)

{

    ucs4 = maptable[(UBYTE)vanilla];

}

I use this method in SSHTerm as libtsm (the terminal emulation layer I am using) works exclusively with unicode as well (see src/term-gc.c).

Topic | Forum

salass00

Re: SSHTerm "Authentication password failed"

Posted on: 4/19 21:29 #7

Just can't stay away

@rjd324

Try specifying the password from the command line.

If it works that way then you are encountering one of the race condition bugs that exists in the latest public version of string.gadget, but should be fixed in the latest beta version.

Topic | Forum

salass00

Re: No std::to_string(float) in GCC 11

Posted on: 3/23 20:34 #8

Just can't stay away

The latest beta version of the AmigaOS 4 newlib port has about 160 added functions compared to the version 53.61 that was released with 4.1 FE update 2. The majority of these are floating point/complex math functions (the complex.h header also exists now) and wide char support functions that are needed for better C++ support in gcc.

Topic | Forum

salass00

Re: Is there a simple why to find the motherboard name?

Posted on: 3/3 20:30 #9

Just can't stay away

@LiveForIt

The IExpansion->GetMachineInfoTags() function with GMIT_MachineString tag should work to get the machine model as a string.

Topic | Forum

salass00

Re: Getting Red Mars to run on AmigaOS 4.1

Posted on: 1/30 14:49 #10

Just can't stay away

@jap

Looks like a random number generator to me, with vposr being used not for timing but to get some extra entropy.

Topic | Forum

salass00

Re: Fading effect on 24bit ARGB screens

Posted on: 1/29 12:58 #11

Just can't stay away

@flash

Quote:

Here is complete C function, it works ok when I use "Win->Width * 4" inside Read/WritePixelArray api calls, but fails if I use Win->RPort->Bitmap->BytesPerRow value.

The BytesPerRow argument is for your own buffer and not for the rastport.

Topic | Forum

salass00

Re: Exodus The Last War patching : work in progress

Posted on: 1/14 8:25 #12

Just can't stay away

@kas1e

Quote:

MOVEA.L 14(A3),A2
BEQ.W LAB_0758
TST.B (A2)
BEQ.W LAB_0758

It looks like maybe the first two instructions were meant to be a NULL pointer check but the programmer did not take into account that moves with an address register as destination do not set condition flags.

On 68020+ I think you can do:
MOVEA.L 14(A3),A2
TST.L A2
BEQ.W LAB_0758

But on 68000 CPU you will have to find a free data register and do something like:
MOVE.L 14(A3),D0
MOVEA.L D0,A2
BEQ.W LAB_0758

Topic | Forum

salass00

Re: Odyssey 1.23 progress: r5 RC2

Posted on: 1/9 21:08 #13

Just can't stay away

@kas1e

Quote:

For me, it reports 210713c, ~35MB.

Only if you use SI units where 1 MB = 1000000 bytes.

Using binary units it is ~33.028 MiB where 1 MiB = 1048576 bytes.

Topic | Forum

salass00

Re: Odyssey 1.23 progress: r5 RC2

Posted on: 1/9 17:36 #14

Just can't stay away

@kas1e

Quote:

@tonyw
Quote:

The binary for Odyssey is huge - some 36 MB. Because it is >32 MB, its PPC FP op-codes can't be translated into SPE op-codes and it will have to run under emulation on the A1222.

36? It is 60 when unstripped, and almost 50 when stripped.

What matters for whether LTE can be used or not isn't executable size but how big the code segment is (".text" section in ELF files).

Running "ppc-amigaos-readelf -e" on the Odyssey exe it reports that the .text section is just a little over 33 MiB.

Topic | Forum

salass00

Re: gcc 9 and 10

Posted on: 12/27 11:20 #15

Just can't stay away

@flash

AFAIK the last gcc to support SPE code generation when using the regular ppc target is gcc 7. For later versions the only way to build SPE code is using a special ppc_spe-<OS>-gcc cross-compiler.

The latest gcc with SPE support that can be built from adtools is gcc 6.4.0.

Topic | Forum

salass00

Re: Qt 6 progress

Posted on: 2021/10/31 19:31 #16

Just can't stay away

@alfkil

Quote:

Here is another one : What is the Amiga equivalent of CLOCK_BOOTTIME ?

In AmigaOS 4 there is GetUpTime() for this.

Topic | Forum

salass00

Re: Cmake and adtools

Posted on: 2021/8/29 9:31 #17

Just can't stay away

@alfkil

Are you using the libstdc++.so that is built along with gcc 11, or are you using the one the one that is supplied with the OS (in SOBJS:)? If it's the latter then that is likely the reason for your problem.

IIRC the newer libstdc++.so is not backwards compatible so the best solution ATM is to bundle it with your program or not use shared objects if possible.

You may also need to update other compiler shared object files like libgcc.so. I'm not sure as I don't use shared objects much anymore.

Topic | Forum

salass00

Re: MutexAttemptWithSignal

Posted on: 2021/8/23 16:22 #18

Just can't stay away

@sTix

To be honest I'm not really sure what the purpose of non-recursive mutices is (as they do not save memory or CPU time AFAIK) and what exactly the correct behavior should be for your code.

What happens however for your code is that after returning from Wait(SIGF_SINGLE|sigmask) MutexAttemptWithSignal() checks if it is now the owner of the mutex in question and if it is it always returns zero indicating that the mutex was successfully obtained.

Topic | Forum

salass00

Re: MutexAttemptWithSignal

Posted on: 2021/8/23 7:34 #19

Just can't stay away

@sTix

The SIGF_SINGLE signal is used internally by the semaphore/mutex functions to signal when a semaphore/mutex has become free so it can't be used in the way that you are using it.

Topic | Forum

salass00

Re: Enhancer Software v2.0 Released

Posted on: 2021/5/21 8:23 #20

Just can't stay away

@Amigo1

Quote:

- Archiver: does not offer the option to assign a default destination dir where the archive should be unarchived to. e.g. UnArc tooltypes (DESTINATION=)

Archiver already supports the ARCHIVE and DESTINATION tooltypes same as UnArc.

The ARCHIVE tooltype can be used to either set an archive that is always opened initially when the program is run or just to set a default path for the ASL requester used for opening archives.

The DESTINATION tooltype sets the initial destination path (default is RAM: if the tooltype is not set).

Quote:

- Archiver: A tooltypes option for Archiver to open at certain coordinates and Window Size would be very handy (See UnArc tooltypes)

You should be able to snapshot/unsnapshot the window from the dropdown menu in the window title bar.

Quote:

- Archiver: IMHO the keyboard shortcuts are a little unconventional; e.g. "l" for "select all"? Why does it not stay close to system style and use "a"?

IIRC "l" is used there because "A" was at some point used for "Extract All". This will be changed in the next version.

Quote:

- Archiver: IMHO, the GUI needs an overhaul. The "Open" button is mispositioned.

Where would you put it then? If it's on a separate row it wastes too much space IMO.

Topic | Forum

Top

(1) 2 3 4 ... 88 »