From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Wilfried Goesgens <w.goesgens@arangodb.org>
Cc: gdb@sourceware.org
Subject: Re: GDB Crashes with V8 & JIT debugging
Date: Wed, 22 Oct 2014 19:08:00 -0000 [thread overview]
Message-ID: <20141022190823.GA7976@host2.jankratochvil.net> (raw)
In-Reply-To: <5447741A.9000000@arangodb.org>
On Wed, 22 Oct 2014 11:08:42 +0200, Wilfried Goesgens wrote:
> https://code.google.com/p/v8/wiki/GDBJITInterface
[...]
> Dwarf Error: Could not find abbrev number 118 [in module <in-memory>]
> Dwarf Error: Could not find abbrev number 267968 [in module <in-memory>]
> Dwarf Error: Could not find abbrev number 58 [in module <in-memory>]
> Dwarf Error: Could not find abbrev number 112 [in module <in-memory>]
> <many similar errors>
> Segmentation fault (core dumped)
GDB dwarf2read.c is not safe against invalid DWARF, it can easily overrun the
input buffers and crash - a sort of DoS. The JIT DWARF generator is probably
buggy (which suggest also the "Could not find abbrev" messages above), for GDB
it is (*) sort-of not a bug.
(*) probably; GDB could have some DWARF reading bug but I find it improbable
for this case.
Jan
prev parent reply other threads:[~2014-10-22 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 9:08 Wilfried Goesgens
2014-10-22 19:08 ` Jan Kratochvil [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141022190823.GA7976@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=w.goesgens@arangodb.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox