[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690
--- Comment #1 from Ben Wiley ---
I get slightly different results when running the same command from the
terminal instead of via CLion:
```bash
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2
times)
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4
times)
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8
times)
eq_SyscallStatus:
{78 0 43}
{78 0 40}
valgrind: m_syswrap/syswrap-main.c:438 (Bool eq_SyscallStatus(UInt,
SyscallStatus *, SyscallStatus *)): the 'impossible' happened.
host stacktrace:
==15943==at 0x258052B8B: ???
==15943==by 0x258052F1C: ???
==15943==by 0x258052EF3: ???
==15943==by 0x2580EC414: ???
==15943==by 0x2580EB9F9: ???
==15943==by 0x2580E9C20: ???
==15943==by 0x2580E83E0: ???
==15943==by 0x2580FA29E: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 771)
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.
```
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 Ben Wiley changed: What|Removed |Added Version|unspecified |3.14 SVN -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 Ben Wiley changed: What|Removed |Added Latest Commit||1ce04c35c2ebbc8ea3c2b38ba69 ||daa9dd40cde35 CC||therealbenwi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 Rhys Kidd changed: What|Removed |Added Assignee|jsew...@acm.org |rhysk...@gmail.com CC||rhysk...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Rhys Kidd --- Hi Ben, Thanks for the bug report and simple reproduction case. Based on the error reports, this looks a lot like a duplicate of a known issue bz#385279. Whilst we haven't quite landed a fix for that one in the development code base - there is a patch with a potential resolution on the linked bug report. If you're able to, testing that patch with your test case would be really helpful. Note that fixing this one issue might expose latter ones -- but at least we will establish whether this initial reported bug is fixed with bz#385279 *** This bug has been marked as a duplicate of bug 385279 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 --- Comment #3 from Ben Wiley --- Hey Rhys, thanks for the patch - I applied it and rebuilt (autogen, configure, make, make install). Unfortunately it does not change anything for me. I get the same error output when I run valgrind memcheck. Were you able to repro my issue on your end? I should note that the two error logs I supplied were apparently related to different issues. The first (from CLion) is when the program is successful until hitting glfwInit(). Any calls to `std::cout << str << "\n";` prior to the bailout are successful. Whereas when I run the same command from the terminal my program appears to not even start (and I get the second error log). Since I'm totally new to valgrind I may have missed a flag specification that works differently between CLion and the default bash environment. I totally copied the flags from CLion and didn't add any on my own. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 Ben Wiley changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #4 from Ben Wiley --- I'm remarking this as 'UNCONFIRMED' since the provided patch didn't work for me. Could someone please follow up? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690
--- Comment #1 from Ben Wiley ---
I get slightly different results when running the same command from the
terminal instead of via CLion:
```bash
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2
times)
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4
times)
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8
times)
eq_SyscallStatus:
{78 0 43}
{78 0 40}
valgrind: m_syswrap/syswrap-main.c:438 (Bool eq_SyscallStatus(UInt,
SyscallStatus *, SyscallStatus *)): the 'impossible' happened.
host stacktrace:
==15943==at 0x258052B8B: ???
==15943==by 0x258052F1C: ???
==15943==by 0x258052EF3: ???
==15943==by 0x2580EC414: ???
==15943==by 0x2580EB9F9: ???
==15943==by 0x2580E9C20: ???
==15943==by 0x2580E83E0: ???
==15943==by 0x2580FA29E: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 771)
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.
```
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 Ben Wiley changed: What|Removed |Added Version|unspecified |3.14 SVN -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 Ben Wiley changed: What|Removed |Added Latest Commit||1ce04c35c2ebbc8ea3c2b38ba69 ||daa9dd40cde35 CC||therealbenwi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 Rhys Kidd changed: What|Removed |Added Assignee|jsew...@acm.org |rhysk...@gmail.com CC||rhysk...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Rhys Kidd --- Hi Ben, Thanks for the bug report and simple reproduction case. Based on the error reports, this looks a lot like a duplicate of a known issue bz#385279. Whilst we haven't quite landed a fix for that one in the development code base - there is a patch with a potential resolution on the linked bug report. If you're able to, testing that patch with your test case would be really helpful. Note that fixing this one issue might expose latter ones -- but at least we will establish whether this initial reported bug is fixed with bz#385279 *** This bug has been marked as a duplicate of bug 385279 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 --- Comment #3 from Ben Wiley --- Hey Rhys, thanks for the patch - I applied it and rebuilt (autogen, configure, make, make install). Unfortunately it does not change anything for me. I get the same error output when I run valgrind memcheck. Were you able to repro my issue on your end? I should note that the two error logs I supplied were apparently related to different issues. The first (from CLion) is when the program is successful until hitting glfwInit(). Any calls to `std::cout << str << "\n";` prior to the bailout are successful. Whereas when I run the same command from the terminal my program appears to not even start (and I get the second error log). Since I'm totally new to valgrind I may have missed a flag specification that works differently between CLion and the default bash environment. I totally copied the flags from CLion and didn't add any on my own. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 387690] glfwInit() causes valgrind to crash
https://bugs.kde.org/show_bug.cgi?id=387690 Ben Wiley changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #4 from Ben Wiley --- I'm remarking this as 'UNCONFIRMED' since the provided patch didn't work for me. Could someone please follow up? Thanks. -- You are receiving this mail because: You are watching all bug changes.
