https://bugs.kde.org/show_bug.cgi?id=399504

            Bug ID: 399504
           Summary: valgrind 3.14rc2 is unable to launch TextEdit.app on
                    macOS 10.12.6
           Product: valgrind
           Version: 3.14 SVN
          Platform: Other
                OS: OS X
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: memcheck
          Assignee: jsew...@acm.org
          Reporter: cwat...@cam.org
  Target Milestone: ---

Created attachment 115480
  --> https://bugs.kde.org/attachment.cgi?id=115480&action=edit
valgrind output running TextEdit

SUMMARY
valgrind 3.14rc2 is unable to launch TextEdit.app on macOS 10.12.6

STEPS TO REPRODUCE
1. just issue: valgrind /Applications/TextEdit.app

OBSERVED RESULT
- various text is output (attached), most notably:

==10558== Thread 2:
==10558== Invalid read of size 4
==10558==    at 0x1077A52B1: ??? (in /usr/lib/system/libsystem_pthread.dylib)
==10558==    by 0x1077A507C: ??? (in /usr/lib/system/libsystem_pthread.dylib)
==10558==  Address 0x18 is not stack'd, malloc'd or (recently) free'd
==10558== 
==10558== 
==10558== Process terminating with default action of signal 11 (SIGSEGV)
==10558==  Access not within mapped region at address 0x18
==10558==    at 0x1077A52B1: ??? (in /usr/lib/system/libsystem_pthread.dylib)
==10558==    by 0x1077A507C: ??? (in /usr/lib/system/libsystem_pthread.dylib)

then the memcheck-amd64-darwin process crashes, see attached backtrace.

EXPECTED RESULT
- to be able to launch TextEdit, probably the simplest Cocoa application.

SOFTWARE VERSIONS
macOS 10.12.6 (16G1510)
valgrind 3.14rc2

ADDITIONAL INFORMATION
- Maybe related to https://bugs.kde.org/show_bug.cgi?id=372779 ?
- I was able to run ls & cat with valgrind, so it's not totally broken
- Calculator.app fails in the same way.
- I suppose it could be identifying a real bug, but TextEdit is pretty
simple... and one supposes these days that Apple uses ASan & TSan...

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to