[cfe-dev] LLVM bug 39720

[Dimitry Andric via cfe-dev]

On 22 Nov 2018, at 12:53, George via cfe-dev <cfe-dev at lists.llvm.org> wrote:
> 
> I am writing here in relation to:
> 
> https://bugs.llvm.org/show_bug.cgi?id=39720
> 
> because of earlier advice given in regards to it:
> 
> On Thu, 15 Nov 2018 15:24:30 +0000 Tim Northover wrote:
> 
>> cfe-dev is a much bigger list, and relevant given
>> that there's a pretty good chance it's an LLVM bug
> 
> On Tue, 20 Nov 2018 11:18:58 -0500 Vedant Kumar wrote:
> 
>> This bug would be a bit easier to triage with a
>> backtrace attached, ideally with some contextual
>> disassembly around the crashing instruction.
> 
> I am not a developer and I don't know how to do that,
> so if any particular info is needed please someone
> ELI5 how to provide it. This is a really critical bug
> in the explained scenario as it results in a
> non-executable binary.

Maybe post that binary and a corresponding core dump somewhere, so
somebody else can load those in a debugger?  Or let your favorite crash
reporting tool (catchsegv or any of the Linux built-in crash reporters)
generate a full report, and post it in the PR?

In any case, you could try the following.  Make sure the gdb package is
installed, then run:

  gdb /opt/ungoogled-chromium/chrome

When gdb is finished loading the executable, type "run", and wait until
the program crashes.  Then execute the following gdb commands:

  bt full
  info registers
  disassemble

and post the full output of those commands in the PR.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20181122/d4aa7851/attachment.sig>