Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-85351

lupdate (qt6 / dev branch) crashes on startup when using LLVM 10.0.1

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • P2: Important
    • None
    • 6.0
    • Tools: Linguist
    • None
    • Linux/Wayland, Linux/X11, Linux/Other display system

    Description

      Running lupdate (after applying the workaround for QTBUG-85348 to make it compile), regardless of parameters, results in

       

      $ /usr/lib64/qt6/bin/lupdate whatever.cpp
      : CommandLine Error: Option 'filter' registered more than once!
      LLVM ERROR: inconsistency in registered CommandLine options
      Segmentation fault (core dumped)
      $ gdb /usr/lib64/qt6/bin/lupdate
      GNU gdb (GDB) 9.2-1 (OpenMandriva Lx release 4.2)
      Copyright (C) 2020 Free Software Foundation, Inc.
      License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
      This is free software: you are free to change and redistribute it.
      There is NO WARRANTY, to the extent permitted by law.
      Type "show copying" and "show warranty" for details.
      This GDB was configured as "x86_64-openmandriva-linux-gnu".
      Type "show configuration" for configuration details.
      For bug reporting instructions, please see:
      <http://www.gnu.org/software/gdb/bugs/>.
      Find the GDB manual and other documentation resources online at:
          <http://www.gnu.org/software/gdb/documentation/>.
      
      For help, type "help".
      Type "apropos word" to search for commands related to "word"...
      Reading symbols from /usr/lib64/qt6/bin/lupdate...
      Reading symbols from .gnu_debugdata for /usr/lib64/qt6/bin/lupdate...
      (No debugging symbols found in .gnu_debugdata for /usr/lib64/qt6/bin/lupdate)
      (gdb) r
      Starting program: /usr/lib64/qt6/bin/lupdate 
      [Thread debugging using libthread_db enabled]
      Using host libthread_db library "/lib64/libthread_db.so.1".
      : CommandLine Error: Option 'filter' registered more than once!
      LLVM ERROR: inconsistency in registered CommandLine options
      
      Program received signal SIGSEGV, Segmentation fault.
      0x00007ffff2ec10de in free () from /lib64/libc.so.6
      (gdb) bt
      #0  0x00007ffff2ec10de in free () from /lib64/libc.so.6
      #1  0x00007ffff262c53f in ?? () from /usr/lib64/libclangFormat.so.10.0
      #2  0x00007ffff2e6cd63 in __run_exit_handlers () from /lib64/libc.so.6
      #3  0x00007ffff2e6cf0c in exit () from /lib64/libc.so.6
      #4  0x00007ffff7f41a44 in llvm::sys::Process::Exit(int) () from /usr/lib64/libLLVMSupport.so.10.0
      #5  0x00007ffff7e6c039 in llvm::report_fatal_error(llvm::Twine const&, bool) () from /usr/lib64/libLLVMSupport.so.10.0
      #6  0x00007ffff7e6bf01 in llvm::report_fatal_error(char const*, bool) () from /usr/lib64/libLLVMSupport.so.10.0
      #7  0x00007ffff7e54b14 in ?? () from /usr/lib64/libLLVMSupport.so.10.0
      #8  0x00007ffff7e45dd4 in ?? () from /usr/lib64/libLLVMSupport.so.10.0
      #9  0x00007ffff7e43e1d in llvm::cl::Option::addArgument() () from /usr/lib64/libLLVMSupport.so.10.0
      #10 0x00007ffff78f3c37 in ?? () from /usr/lib64/libclangTooling.so.10.0
      #11 0x00007ffff78f7876 in ?? () from /usr/lib64/libclangTooling.so.10.0
      #12 0x00007ffff7fe1dae in call_init () from /lib64/ld-linux-x86-64.so.2
      #13 0x00007ffff7fe1e8c in _dl_init () from /lib64/ld-linux-x86-64.so.2
      #14 0x00007ffff7fd20ca in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
      #15 0x0000000000000001 in ?? ()
      #16 0x00007fffffffd969 in ?? ()
      #17 0x0000000000000000 in ?? ()
      

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            kkohne Kai Köhne
            bero Bernhard Rosenkränzer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes