Launchpad has imported 6 comments from the remote bug at http://llvm.org/bugs/show_bug.cgi?id=20768.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2014-08-27T13:50:23+00:00 Qbvui+9baubb2cfhobc wrote: Created attachment 12939 A "hello world" program that LLDB should be capable of debugging, but instead complains that it doesn't "contain" the right architecture. Debian's LLDB 3.3 was able to load executables, but the latest Debian release produces this error, and so does a freshly-built binary from the SVN repository. This error message is Google-proof. I can't find any information at all as to a possible cause. Reply at: https://bugs.launchpad.net/ubuntu/+source/llvm- toolchain-3.5/+bug/1385876/comments/0 ------------------------------------------------------------------------ On 2014-08-27T15:23:25+00:00 Qbvui+9baubb2cfhobc wrote: Created attachment 12940 Another ELF binary, this time compiled with clang instead of GCC Reply at: https://bugs.launchpad.net/ubuntu/+source/llvm- toolchain-3.5/+bug/1385876/comments/1 ------------------------------------------------------------------------ On 2014-08-27T15:23:50+00:00 Qbvui+9baubb2cfhobc wrote: Created attachment 12941 Source code for both ELF binaries Reply at: https://bugs.launchpad.net/ubuntu/+source/llvm- toolchain-3.5/+bug/1385876/comments/2 ------------------------------------------------------------------------ On 2014-08-27T15:54:56+00:00 Qbvui+9baubb2cfhobc wrote: I'm going through the source code right now, and it turns out that there are about a million possible reasons why this error message might be generated, none of which are reported in any way at the point where these errors are generated. What this message really means is "Some error occurred, somewhere in the code, for some reason. Maybe the file couldn't be opened, or maybe it wasn't in the right format, or maybe it was something else entirely. Who knows?" I'll just sprinkle some fprintf's into ObjectFile::FindPlugin, and then maybe I'll actually know something. Worst. Error-hiding. Ever. Reply at: https://bugs.launchpad.net/ubuntu/+source/llvm- toolchain-3.5/+bug/1385876/comments/3 ------------------------------------------------------------------------ On 2014-08-28T21:12:50+00:00 Qbvui+9baubb2cfhobc wrote: Fuck it, I can't figure out how this thing works. It seems to be expecting "something" to be in the executables that it isn't finding. So I'll just go play with LLDB 3.3 now. Reply at: https://bugs.launchpad.net/ubuntu/+source/llvm- toolchain-3.5/+bug/1385876/comments/4 ------------------------------------------------------------------------ On 2014-11-23T15:37:48+00:00 Yury-meshkov wrote: I have the same issue on Ubuntu 14.10 32bit. But lldb works fine on my Ubuntu 64bit. This bug makes LLDB on Linux 32bit unusable completely. Reply at: https://bugs.launchpad.net/ubuntu/+source/llvm- toolchain-3.5/+bug/1385876/comments/9 ** Changed in: llvm Status: Unknown => Confirmed ** Changed in: llvm Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385876 Title: lldb fails to start with 'doesn't contain the architecture x86_64' To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1385876/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
