From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH v2 2/2] Add Rust support to source highlighting
Date: Wed, 04 Sep 2019 17:22:00 -0000 [thread overview]
Message-ID: <332da42c-ae75-a148-221f-4f7bb815f40f@suse.de> (raw)
In-Reply-To: <20190727155155.32417-3-tom@tromey.com>
On 27-07-19 17:51, Tom Tromey wrote:
> Currently, no release of GNU Source Highlight supports Rust. However,
> I've checked in a patch to do so there, and I plan to make a new
> release sometime this summer.
>
> This patch prepares gdb for that by adding support for Rust to the
> source highlighting code.
>
> Because Source Highlight will throw an exception if the language is
> unrecognized, this also changes gdb to ignore exceptions here. This
> will cause gdb to fall back to un-highlighted source text.
>
> This updates gdb's configure script to reject the combination of
> Source Highlight and -static-libstdc++. This is done because it's not
> possible to use -static-libstdc++ and then catch exceptions from a
> shared library.
>
> Tested with the current and development versions of Source Highlight.
Hi,
I recently updated my regular build setup to include an installed
libsource-highlight.so by installing package libsource-highlight-devel
in openSUSE Leap 15.1.
Subsequently I ran into this error in the gdb 8.3 branch:
...
$ ./install/bin/gdb -q a.out -ex start
Reading symbols from a.out...
Temporary breakpoint 1 at 0x40053b: file hello.c, line 9.
Starting program: /data/gdb_versions/devel/a.out
Temporary breakpoint 1, main () at hello.c:9
terminate called after throwing an instance of 'srchilite::ParserException'
what(): error during the parsing of a definition file
Aborted (core dumped)
...
This expection happens when the library attempts to access
/usr/share/source-highlight/esc.outlang, which is not there, because
it's contained in another package (source-highlight). Installing that
package fixes the error.
Nevertheless, the error did not occur on master, and I've bisect that
behaviour to this patch.
So my question is: does it make sense to backport (part of) this patch
to 8.3?
Thanks,
- Tom
next prev parent reply other threads:[~2019-09-04 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 15:52 [PATCH v2 0/2] " Tom Tromey
2019-07-27 15:52 ` [PATCH v2 1/2] Add --with-static-standard-libraries to the top level Tom Tromey
2019-07-27 15:52 ` [PATCH v2 2/2] Add Rust support to source highlighting Tom Tromey
2019-09-04 17:22 ` Tom de Vries [this message]
2019-09-10 15:56 ` Tom Tromey
2019-09-12 19:20 ` Tom de Vries
2019-09-17 18:24 ` Tom Tromey
2019-09-18 22:16 ` Tom de Vries
2019-09-19 12:54 ` Tom Tromey
2019-09-19 16:18 ` [PATCH][gdb] Catch exception when constructing the highlighter Tom de Vries
2019-08-19 16:19 ` [PATCH v2 0/2] Add Rust support to source highlighting Tom Tromey
2019-08-19 18:29 ` Pedro Alves
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=332da42c-ae75-a148-221f-4f7bb815f40f@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tom@tromey.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