HT204563: About Security Update 2015-003

Learn about About Security Update 2015-003
nicolasfrombordeaux

Q: Bash crashes after installing Security Update 2015-003

Immediately after installing Security Update 2015-003 and rebooting, bash stopped working.

 

Each time I tried to open Terminal, the (empty) window stayed open for some seconds, to eventually close itself. The same happened with iTerm2.

 

I changed to tcsh (Systems Preferences -> Users -> Unlock -> ctrl+click over my User -> Advanced Options -> Login shell -> /bin/tcsh, so I was able to open terminals after this change.

 

If I try to run bash on tcsh, bash crashes with a "Segmentation Fault". Running in verbose mode, I get:

'bash -v ' terminated by signal SIGSEGV (Address boundary error)

 

bash is very important for my work so, can anybody please help me to get it working again?

Thanks

 

Nicolas Loira

MacBook Pro with Retina display, OS X Yosemite (10.10.2)

Posted on Mar 24, 2015 10:58 AM

Close

Q: Bash crashes after installing Security Update 2015-003

  • All replies
  • Helpful answers

  • by PATRICKMELE,

    PATRICKMELE PATRICKMELE Mar 24, 2015 11:13 AM in response to nicolasfrombordeaux
    Level 3 (909 points)
    Mac OS X
    Mar 24, 2015 11:13 AM in response to nicolasfrombordeaux
  • by Linc Davis,

    Linc Davis Linc Davis Mar 24, 2015 1:31 PM in response to nicolasfrombordeaux
    Level 10 (208,005 points)
    Applications
    Mar 24, 2015 1:31 PM in response to nicolasfrombordeaux

    Launch the Console application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad and start typing the name.

    Step 1

    For this step, the title of the Console window should be All Messages. If it isn't, select

              SYSTEM LOG QUERIES All Messages

    from the log list on the left. If you don't see that list, select

              View Show Log List

    from the menu bar at the top of the screen.

    In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

    Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

    ☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

    Please don't indiscriminately dump thousands of lines from the log into this discussion.

    Please don't post screenshots of log messages—post the text.

    ☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

    Step 2

    In the Console window, select

              DIAGNOSTIC AND USAGE INFORMATION User Diagnostic Reports

    (not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

    I know the report is long, maybe several hundred lines. Please post all of it anyway.

    If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

    Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.