Comment 11 for bug 2058191

Reading my crash dump, i noticed a interesting thing. Here is the back trace:

Downloading separate debug info for system-supplied DSO at 0x7ffe5ecc5000
Core was generated by `/opt/brave.com/brave/brave --type=renderer --crashpad-handler-pid=5837 --enable'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000058e16cb3b49e in ?? ()
[Current thread is 1 (LWP 1)]
(gdb) bt
#0 0x000058e16cb3b49e in ?? ()
#1 0x00007ffe5ec93780 in ?? ()
#2 0x0000000000000000 in ?? ()

The first backtrace is located inside the brave binary as (gdb) info proc mappings says:
Mapped address spaces:

          Start Addr End Addr Size Offset objfile
               [...]
      0x58e16bb4b000 0x58e1778ad000 0xbd62000 0x2e1c000 /opt/brave.com/brave/brave
               [...]

The second backtrace doesn't show in the mapped address list. But as the previous output says it's related to a "system-supplied DSO". I Googled it and a guy named fche on stackoverflow said "system-supplied-DSO means a shared library provided directly by the linux kernel such as VDSO". Is this right?

If that's true, does this mean we have a big kernel issue?