std.testing.allocator OutOfMemory error | Zig Programming Language | Page 1

tardy umbra Sep 9, 2024, 7:09 PM

#

std.testing.allocator shouldn't oom? is it possible you're getting a stacktrace with error.OutOfMemory at the top but it's a corrupted error trace and it actually starts below that one?

#

or are you hitting a panic?

shrewd cloud Sep 9, 2024, 7:10 PM

#

im hitting a panic because of OOM

#

    /// Resets the text output device hardware.
    pub fn reset(self: *const SimpleTextOutput, verify: bool) callconv (uefi.cc) Status {
        const parent_self: *__Testing_SimpleTextOutput = @constCast(@fieldParentPtr("interface", self));
        parent_self.eventList.append(.{
            .Reset = ResetEvent{
                .result = Status.Success,
                .verify = verify,
            }
        }) catch @panic("Failed to append");

        parent_self.mode.cursor_column = 0;
        parent_self.mode.cursor_row = 0;
        parent_self.mode.attribute = 0x07;

        return Status.Success;
    }

#

📎 test_failure.txt

#

Current Interface heirarchy. The relay device is currently using the mock testing device where their implementations should be 1:1 in terms of content captured. In the relay test, it calls the underlaying device implementation and then records the state returned to it. The underlying device is the one currently panicing here, however, the device passes all known failure cases so im not sure why memory allocation is failing

#

full source code

📎 uefi.tar.gz

tardy umbra Sep 9, 2024, 7:39 PM

#

is it possible one of the pointer casts is messed up and so the allocator is holding bad data?

#std.testing.allocator OutOfMemory error