Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-37303

GDB fails to read the memory addresses on Ubuntu 18.04

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • Labels:
      None
    • ALL
    • 55

      GDB can't read the memory addresses of threads that are holding the MongoDB locks. Here's the hang analyzer's output.

      [2018/09/14 02:54:57.964] Running Hang Analyzer Supplement - MongoDBDumpLocks
      [2018/09/14 02:54:58.591] Ignoring error 'Couldn't write extended state status: Bad address.' in dump_mongod_locks
      [2018/09/14 02:54:58.621] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.651] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.681] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.710] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.740] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.770] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.799] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.829] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.858] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.888] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.918] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.948] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:58.978] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.008] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.037] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.078] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.108] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.138] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.168] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.198] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.228] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.257] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.287] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.316] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.346] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.376] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.405] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.435] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.466] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.495] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.525] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.555] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.585] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.614] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.644] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.674] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.704] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.733] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.763] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.804] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.844] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.874] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.904] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.933] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.963] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:54:59.994] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:00.025] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:00.055] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:00.085] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:00.360] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:00.464] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:00.515] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:00.566] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.238] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.269] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.300] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.330] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.360] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.390] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.420] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.450] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.481] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.511] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.541] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.571] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.601] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.631] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.661] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.692] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.732] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.762] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.792] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.822] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.852] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.883] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.913] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.943] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:01.974] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.004] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.035] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.065] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.095] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.126] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.156] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.186] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.216] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.246] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.276] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.306] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.336] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.367] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.397] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.427] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.469] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.510] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.540] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.570] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.600] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.631] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.662] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.692] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.725] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:02.756] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:03.034] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:03.139] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:03.190] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:03.241] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:04.570] Ignoring GDB error 'Couldn't write extended state status: Bad address.' in get_locks
      [2018/09/14 02:55:04.570] Not generating the digraph, since the lock graph is empty
      [2018/09/14 02:55:04.570] Running Print JavaScript Stack Supplement
      [2018/09/14 02:55:04.570] Detaching from program: /data/mci/d36c94dc43ac35832efb87229845fa9f/src/mongod, process 26138
      [2018/09/14 02:55:04.971] Done analyzing mongod process with PID 26138
      

            Assignee:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: