bug-gnu-pspp
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PSPP-BUG: Bug report for GNU pspp 2.0.1


From: Ben Pfaff
Subject: Re: PSPP-BUG: Bug report for GNU pspp 2.0.1
Date: Sun, 11 Aug 2024 11:54:50 -0700

It looks like the syntax you gave to PSPP asked it to allocate a
matrix that will not fit in memory. I'm not interested in this kind of
bug report because "fixing" it would require PSPP to put arbitrary
limits on the sizes of matrices.

On Sun, Aug 11, 2024 at 7:13 AM Suyue Guo <suyuee.guo@gmail.com> wrote:
>
> Dear maintainers of pspp:
>
> A bug was found in pspp 2.0.1.
>
> The poc to trigger this bug is in the attached file.
>
> command to run:
> pspp crash_poc
>
> output:
>
> ./crash_poc:1.2: error: Unknown command `-'.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.9-1.10: error: Bad character U+FFFD in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.10-1.11: error: Bad character U+FFFD in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.12-1.13: error: Bad character U+FFFD in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.13: error: Bad character U+0004 in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.13-1.14: error: Bad character U+FFFD in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.14-1.15: error: Bad character U+FFFD in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.15-1.16: error: Bad character U+FFFD in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.16-1.17: error: Bad character U+FFFD in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.19: error: Bad character U+0000 in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.19: error: Bad character U+0000 in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.20-1.21: error: Bad character U+FFFD in input.
>
>     1 | ---.----NeT
>
>
> ./crash_poc:1.21-1.22: error: Bad character U+FFFD in input.
>
>     1 | ---.----NeT
>
> ******************************************************
>
> You have discovered a bug in PSPP.  Please report this
>
> to bug-gnu-pspp@gnu.org.  Please include this entire
>
> message, *plus* several lines of output just above it.
>
> For the best chance at having the bug fixed, also
>
> include the syntax file that triggered it and a sample
>
> of any data file used for input.
>
> proximate cause:     Segmentation Violation
>
> version:             GNU pspp 2.0.1
>
> host_system:         x86_64-pc-linux-gnu
>
> build_system:        x86_64-pc-linux-gnu
>
> locale_dir:          /usr/local/share/locale
>
> compiler version:    11.4.0
>
> ******************************************************
>
> Segmentation fault (core dumped)
>
>
>
> asan output:
>
> =================================================================
>
> ==2548843==ERROR: AddressSanitizer: requested allocation size 0x26ce1b82048 
> (0x26ce1b83048 after adjustments for alignment, red zones etc.) exceeds 
> maximum supported size of 0x10000000000 (thread T0)
>
>     #0 0x7f841fe4f887 in __interceptor_malloc 
> ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
>
>     #1 0x7f841f54c4cc in gsl_block_alloc 
> (/lib/x86_64-linux-gnu/libgsl.so.27+0x5e4cc)
>
>
> ==2548843==HINT: if you don't care about these errors you may set 
> allocator_may_return_null=1
>
> SUMMARY: AddressSanitizer: allocation-size-too-big 
> ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145 in 
> __interceptor_malloc
>
> ==2548843==ABORTING
>
> _______________________________________________
> Bug-gnu-pspp mailing list
> Bug-gnu-pspp@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-gnu-pspp



reply via email to

[Prev in Thread] Current Thread [Next in Thread]