From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: libor.bukata@oracle.com
Cc: gdb-patches@sourceware.org
Subject: Re: Fix a crash in compile_to_object function
Date: Mon, 09 Sep 2019 08:07:00 -0000 [thread overview]
Message-ID: <yddmufdriyo.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <3ad99625-43ff-a450-6e50-d83242224443@oracle.com> (libor bukata's message of "Fri, 6 Sep 2019 15:37:33 +0200")
Hi Libor,
> On non-Linux platforms, gdb crashes when compile command is issued
> because of the null pointer in struct osabi_names gdb_osab. The attached
> patch adds a check to avoid this crash and adds osabi name for Solaris.
> However, there is probably more work required to enable compile feature
> on Solaris (e.g., solaris_infcall_munmap) and other platforms.
just out of curiosity: what prompted you to try this?
I gave it a very quick whirl myself, trying to run the
gdb.compile/compile.exp test on amd64-pc-solaris2.11 with gdb master and
libcc1.so from gcc mainline: all I got was a SIGTRAP from the very first
compile command.
That said, I'm quite unlikely to work on this any time soon: with
ca. 2500 failures in the gdb testsuite on Solaris and even basic
features unimplented (e.g. I'm currently looking into TLS support), I
believe there are way more pressing issues. However, if you want to
give it a try yourself, I'm more than happy to help get a patch in.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2019-09-09 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 13:37 libor.bukata
2019-09-06 16:42 ` Keith Seitz
2019-09-06 17:11 ` libor.bukata
2019-09-09 17:56 ` Tom Tromey
2019-09-09 8:07 ` Rainer Orth [this message]
2019-09-09 8:57 ` libor.bukata
2019-09-10 9:18 ` Rainer Orth
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=yddmufdriyo.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb-patches@sourceware.org \
--cc=libor.bukata@oracle.com \
/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