Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Tom Tromey <tom@tromey.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: static linking of gdb
Date: Mon, 6 Apr 2020 15:45:23 +0200	[thread overview]
Message-ID: <AM6PR03MB5170DE3A69633C7CC1ED728EE4C20@AM6PR03MB5170.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <87r1x0hgs7.fsf@tromey.com>



On 4/6/20 3:42 PM, Tom Tromey wrote:
>>>>>> "Bernd" == Bernd Edlinger <bernd.edlinger@hotmail.de> writes:
> 
>>> gdb should normally not be linked with -static-libstdc++.  Currently
>>> this has not caused problems, but it's incompatible with catching an
>>> exception thrown from a shared library -- and a subsequent patch
>>> changes gdb to do just this.
> 
> Bernd> Now this makes me a bit nervios.
> 
> Bernd> Tom can you explain where this might happen?
> 
> The source highlight library throws exceptions as part of its API.
> 

Yes, understood, but why dont you catch them from a shared object,
and return normal return codes, if you like you can throw the same
exception from the static plugin layer ?

> I hadn't considered it.

You definitely should,  it is never too late to correct a wrong decision.
Not being able to link gdb statically is a major usability-regression.


Bernd.

> Tom
> 


  reply	other threads:[~2020-04-06 13:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05 10:13 Bernd Edlinger
2020-04-05 13:17 ` Eli Zaretskii
2020-04-05 13:23   ` Bernd Edlinger
2020-04-05 13:48   ` Bernd Edlinger
2020-04-05 14:19     ` Eli Zaretskii
2020-04-05 14:56       ` Bernd Edlinger
2020-04-06  3:27   ` Bernd Edlinger
2020-04-06  7:14     ` Bernd Edlinger
2020-04-06 13:43       ` Tom Tromey
2020-04-06 13:42     ` Tom Tromey
2020-04-06 13:45       ` Bernd Edlinger [this message]
2020-04-06 14:11         ` Tom Tromey

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=AM6PR03MB5170DE3A69633C7CC1ED728EE4C20@AM6PR03MB5170.eurprd03.prod.outlook.com \
    --to=bernd.edlinger@hotmail.de \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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