<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/check/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/check/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 16 Aug 2024 04:40:12 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/check/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>Check tutorial fails with clang memory sanitization</title><link>https://sourceforge.net/p/check/bugs/116/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When running the tutorial project while compiling with clang v18.1.8's memory sanitizer, the result is a panic in the ppack() function for writing unitialized memory with fwrite(). Manual inspection tells me that the memory in question is in fact initialized, and valgrind confirms that there is no use of unitialized memory, so this is ultimately an issue with clang's memory sanitizer, but is nonetheless annoying. I have confirmed that setting all the memory allocated in emalloc() to 0xAA (or any other value) fixes this issue, however if memory is allocated in erealloc(), I was able to confirm that the same issue would occur, and making erealloc() capable of initializing all the excess memory required me to change the signature of the function, which might be a breaking change.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">empathica</dc:creator><pubDate>Fri, 16 Aug 2024 04:40:12 -0000</pubDate><guid>https://sourceforge.net2a099d01a8594fdfbb6bddf2c08c9ef346e7102d</guid></item><item><title>make check failing</title><link>https://sourceforge.net/p/check/bugs/115/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Check 0.15.2:&lt;br/&gt;
Failing the &lt;code&gt;make check&lt;/code&gt; test&lt;/p&gt;
&lt;p&gt;attached log.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">DMagician</dc:creator><pubDate>Sun, 31 Dec 2023 11:25:38 -0000</pubDate><guid>https://sourceforge.net656544cadb18ef68b8880464785330a8f496715d</guid></item><item><title>#111 "No messaging setup" in check_msg causes test failure</title><link>https://sourceforge.net/p/check/bugs/111/?limit=25#1310</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;continuing at &lt;a href="https://github.com/libcheck/check/issues/18" rel="nofollow"&gt;https://github.com/libcheck/check/issues/18&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kalle Richter</dc:creator><pubDate>Sun, 07 Feb 2016 21:45:33 -0000</pubDate><guid>https://sourceforge.netbdd0762bd6c2deb951cb3690c3106690e60f6aae</guid></item><item><title>Visual Studio 14(2015) Compiling</title><link>https://sourceforge.net/p/check/bugs/114/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Errors while building project with Visual Studio 14(2015). Problem with redefinition. Macro definition of snprintf conflicts with Standard Library function declaration.&lt;/p&gt;
&lt;p&gt;Note:&lt;br/&gt;
Visual Studio 14 defines snprintf()..&lt;/p&gt;&lt;/div&gt;</description><pubDate>Thu, 28 Jan 2016 15:58:04 -0000</pubDate><guid>https://sourceforge.net7546dd752f53c3f1bff9c88dd22fb1305e3275a5</guid></item><item><title>#111 "No messaging setup" in check_msg causes test failure</title><link>https://sourceforge.net/p/check/bugs/111/?limit=25#fa0a</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Branden Archer</dc:creator><pubDate>Fri, 25 Dec 2015 23:14:55 -0000</pubDate><guid>https://sourceforge.netff70de9a43f7af80cbbb02c8434b74ec35a37a76</guid></item><item><title>#108 Available timer clock types not properly identified at runtime</title><link>https://sourceforge.net/p/check/bugs/108/?limit=25#66ed</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed-wont-fix&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Branden Archer</dc:creator><pubDate>Fri, 25 Dec 2015 23:11:42 -0000</pubDate><guid>https://sourceforge.netb747a8d335b205d5f5a84c55671313c18b15179a</guid></item><item><title>#107 Please add __attribute__((__format__ (__printf__, ))) to _ck_assert_failed</title><link>https://sourceforge.net/p/check/bugs/107/?limit=25#dbd3</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed-postponed&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Branden Archer</dc:creator><pubDate>Fri, 25 Dec 2015 23:06:40 -0000</pubDate><guid>https://sourceforge.net713c7cb52464a2783f71ef7a5bd5eb078e9e98a7</guid></item><item><title>#113 ASAN Reported ASAN:SIGSEGV</title><link>https://sourceforge.net/p/check/bugs/113/?limit=25#b543</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed-wont-fix&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Branden Archer</dc:creator><pubDate>Thu, 26 Nov 2015 17:37:56 -0000</pubDate><guid>https://sourceforge.net48a225c17a62dcc215ad6e295db0afc4c58fd336</guid></item><item><title>#113 ASAN Reported ASAN:SIGSEGV</title><link>https://sourceforge.net/p/check/bugs/113/?limit=25#2e0a</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Gaurav,&lt;/p&gt;
&lt;p&gt;Thanks for the bug report. &lt;/p&gt;
&lt;p&gt;I've not used ASAN before, but from what I've read and understand one thing it will attempt to do is report when and where a process throws a signal, right? The issue you mentioned I can reproduce on my system. I think that the specific test which is failing is intentionally throwing the SEGV signal and showing that the test framework can properly detect it. One example is the &lt;br/&gt;
   test_segv_pass &lt;br/&gt;
test here:&lt;br/&gt;
&lt;a href="http://sourceforge.net/p/check/code/HEAD/tree/trunk/tests/check_check_sub.c#l545"&gt;http://sourceforge.net/p/check/code/HEAD/tree/trunk/tests/check_check_sub.c#l545&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I think that ASAN is catching those signals, which are actually intentional.&lt;/p&gt;
&lt;p&gt;However, if you are able to find a minimal program which does not intentionally throw a signal and ASAN finds an issue, kindly let us know.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Branden Archer</dc:creator><pubDate>Thu, 26 Nov 2015 17:37:36 -0000</pubDate><guid>https://sourceforge.net4d92437ab21058cf1000aa264d62b3c719c0c723</guid></item><item><title>ASAN Reported ASAN:SIGSEGV</title><link>https://sourceforge.net/p/check/bugs/113/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Build using - ./configure CFLAGS="-fsanitize=address -g" LDFLAGS="-fsanitize=address" &amp;amp;&amp;amp; make.&lt;br/&gt;
Then do  "make check"&lt;br/&gt;
It reports below error:&lt;br/&gt;
FAIL: check_check_export&lt;br/&gt;
Running suite(s): Fork Sub&lt;br/&gt;
100%: Checks: 3, Failures: 0, Errors: 0&lt;br/&gt;
check_check_fork.c:18:P:Core:test_inc:0: Passed&lt;br/&gt;
check_check_fork.c:27:P:Core:test_nofork_sideeffects:0: Passed&lt;br/&gt;
check_check_fork.c:34:P:Core:test_nofork_pid:0: Passed&lt;br/&gt;
Running suite(s): Fix Sub&lt;br/&gt;
0%: Checks: 1, Failures: 1, Errors: 0&lt;br/&gt;
check_check_fixture.c:16:S:Fix Sub:unchecked_setup:0: Test failure in fixture&lt;br/&gt;
Running suite(s): Check Servant&lt;br/&gt;
ASAN:SIGSEGV&lt;br/&gt;
=================================================================&lt;br/&gt;
==21922== ERROR: AddressSanitizer: SEGV on unknown address 0x040b000055a2 (pc 0x2acaa8b5620b sp 0x7fff16a2c4a8 bp 0x7fff16a2c4c0 T0)&lt;br/&gt;
AddressSanitizer can not provide additional info.&lt;br/&gt;
    #0 0x2acaa8b5620a (/lib/x86_64-linux-gnu/libpthread-2.19.so+0x1020a)&lt;br/&gt;
    #1 0x4061a3 (/home4/check-0.10.0/tests/check_check+0x4061a3)&lt;br/&gt;
    #2 0x41c5b0 (/home4/check-0.10.0/tests/check_check+0x41c5b0)&lt;br/&gt;
    #3 0x41b582 (/home4/check-0.10.0/tests/check_check+0x41b582)&lt;br/&gt;
    #4 0x41bd94 (/home4/check-0.10.0/tests/check_check+0x41bd94)&lt;br/&gt;
    #5 0x41b433 (/home4/check-0.10.0/tests/check_check+0x41b433)&lt;br/&gt;
    #6 0x41df17 (/home4/check-0.10.0/tests/check_check+0x41df17)&lt;br/&gt;
    #7 0x41dbf3 (/home4/check-0.10.0/tests/check_check+0x41dbf3)&lt;br/&gt;
    #8 0x40a2ac (/home4/check-0.10.0/tests/check_check+0x40a2ac)&lt;br/&gt;
    #9 0x4130f1 (/home4/check-0.10.0/tests/check_check+0x4130f1)&lt;br/&gt;
    #10 0x2acaa8d85ec4 (/lib/x86_64-linux-gnu/libc-2.19.so+0x21ec4)&lt;br/&gt;
    #11 0x401f78 (/home4/check-0.10.0/tests/check_check+0x401f78)&lt;br/&gt;
==21922== ABORTING&lt;br/&gt;
ASAN:SIGSEGV&lt;br/&gt;
=================================================================&lt;br/&gt;
==21923== ERROR: AddressSanitizer: SEGV on unknown address 0x040b000055a3 (pc 0x2acaa8b5620b sp 0x7fff16a2c4a8 bp 0x7fff16a2c4c0 T0)&lt;br/&gt;
AddressSanitizer can not provide additional info.&lt;br/&gt;
    #0 0x2acaa8b5620a (/lib/x86_64-linux-gnu/libpthread-2.19.so+0x1020a)&lt;br/&gt;
    #1 0x40616e (/home4/check-0.10.0/tests/check_check+0x40616e)&lt;br/&gt;
    #2 0x41c5b0 (/home4/check-0.10.0/tests/check_check+0x41c5b0)&lt;br/&gt;
    #3 0x41b582 (/home4/check-0.10.0/tests/check_check+0x41b582)&lt;br/&gt;
    #4 0x41bd94 (/home4/check-0.10.0/tests/check_check+0x41bd94)&lt;br/&gt;
    #5 0x41b433 (/home4/check-0.10.0/tests/check_check+0x41b433)&lt;br/&gt;
    #6 0x41df17 (/home4/check-0.10.0/tests/check_check+0x41df17)&lt;br/&gt;
    #7 0x41dbf3 (/home4/check-0.10.0/tests/check_check+0x41dbf3)&lt;br/&gt;
    #8 0x40a2ac (/home4/check-0.10.0/tests/check_check+0x40a2ac)&lt;br/&gt;
    #9 0x4130f1 (/home4/check-0.10.0/tests/check_check+0x4130f1)&lt;br/&gt;
    #10 0x2acaa8d85ec4 (/lib/x86_64-linux-gnu/libc-2.19.so+0x21ec4)&lt;br/&gt;
    #11 0x401f78 (/home4/check-0.10.0/tests/check_check+0x401f78)&lt;br/&gt;
==21923== ABORTING&lt;br/&gt;
ASAN:SIGSEGV&lt;br/&gt;
=================================================================&lt;br/&gt;
==21924== ERROR: AddressSanitizer: SEGV on unknown address 0x040b000055a4 (pc 0x2acaa8b5620b sp 0x7fff16a2c4a8 bp 0x7fff16a2c4c0 T0)&lt;br/&gt;
AddressSanitizer can not provide additional info.&lt;br/&gt;
    #0 0x2acaa8b5620a (/lib/x86_64-linux-gnu/libpthread-2.19.so+0x1020a)&lt;br/&gt;
    #1 0x4061a3 (/home4/check-0.10.0/tests/check_check+0x4061a3)&lt;br/&gt;
    #2 0x41c5b0 (/home4/check-0.10.0/tests/check_check+0x41c5b0)&lt;br/&gt;
    #3 0x41b582 (/home4/check-0.10.0/tests/check_check+0x41b582)&lt;br/&gt;
    #4 0x41bd94 (/home4/check-0.10.0/tests/check_check+0x41bd94)&lt;br/&gt;
    #5 0x41b433 (/home4/check-0.10.0/tests/check_check+0x41b433)&lt;br/&gt;
    #6 0x41df17 (/home4/check-0.10.0/tests/check_check+0x41df17)&lt;br/&gt;
    #7 0x41dbf3 (/home4/check-0.10.0/tests/check_check+0x41dbf3)&lt;br/&gt;
    #8 0x40a2ac (/home4/check-0.10.0/tests/check_check+0x40a2ac)&lt;br/&gt;
    #9 0x4130f1 (/home4/check-0.10.0/tests/check_check+0x4130f1)&lt;br/&gt;
    #10 0x2acaa8d85ec4 (/lib/x86_64-linux-gnu/libc-2.19.so+0x21ec4)&lt;br/&gt;
    #11 0x401f78 (/home4/check-0.10.0/tests/check_check+0x401f78)&lt;br/&gt;
==21924== ABORTING&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gaurav</dc:creator><pubDate>Tue, 24 Nov 2015 03:25:57 -0000</pubDate><guid>https://sourceforge.neta0be35e0d7508e570904c098dd8195395e27abe1</guid></item></channel></rss>