Bug 364359 - Valgrind crashes on fcntl(F_SETFL, O_NONBLOCK, fd)
Summary: Valgrind crashes on fcntl(F_SETFL, O_NONBLOCK, fd)
Status: RESOLVED WORKSFORME
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (other bugs)
Version First Reported In: 3.11.0
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-15 19:13 UTC by Robert Xu
Modified: 2023-03-07 03:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Xu 2016-06-15 19:13:13 UTC
Running valgrind tests for something I'm working on - valgrind crashes on a fcntl call:

FAIL: bash
==========

==27992== Memcheck, a memory error detector
==27992== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==27992== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==27992== Command: /home/ubuntu/slip/tests/.libs/lt-bash
==27992==
..not caught
....
valgrind: m_syswrap/syswrap-linux.c:5361 (vgSysWrap_linux_sys_fcntl_before): Assertion 'Unimplemented functionality' failed.
valgrind: valgrind

host stacktrace:
==27992==    at 0x38074022: show_sched_status_wrk (m_libcassert.c:343)
==27992==    by 0x380742BA: report_and_quit (m_libcassert.c:415)
==27992==    by 0x38074491: vgPlain_assert_fail (m_libcassert.c:481)
==27992==    by 0x380D3844: vgSysWrap_linux_sys_fcntl_before (syswrap-linux.c:5361)
==27992==    by 0x380B481F: vgPlain_client_syscall (syswrap-main.c:1905)
==27992==    by 0x380B1B07: handle_syscall (scheduler.c:1118)
==27992==    by 0x380B34E1: vgPlain_scheduler (scheduler.c:1435)
==27992==    by 0x380BF941: thread_wrapper (syswrap-linux.c:102)
==27992==    by 0x380BF941: run_a_thread_NORETURN (syswrap-linux.c:155)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 27992)
==27992==    at 0x5ACEB8F: do_fcntl (fcntl.c:39)
==27992==    by 0x5ACEB8F: fcntl (fcntl.c:88)
==27992==    by 0x5342C1F: bash_system_excl (bash.c:73)
==27992==    by 0x4011F9: BashSystemExcl (bash.c:41)
==27992==    by 0x401C15: suite (bash.c:101)
==27992==    by 0x401D7E: main (bash.c:106)


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.

FAIL bash (exit status: 1)

The relevant line of bash_system_excl:73 is fcntl(F_SETFL, O_NONBLOCK, inPipeFds[0]).
Interestingly enough, I do not see any issue with this when I run Valgrind under OS X Homebrew.
Running Valgrind on Ubuntu 14.04, Linuxbrew, 3.11.0.
Comment 1 Ivo Raisr 2017-05-05 14:17:40 UTC
fcntl(F_SETFL) has been implemented for a long time.
Could you please try again with a recent Valgrind, ideally built from upstream SVN?
Comment 2 Paul Floyd 2023-02-05 21:01:17 UTC
No answer for 6 years.
Comment 3 Bug Janitor Service 2023-02-20 03:45:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2023-03-07 03:45:38 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!