Date: Tue, 2 Feb 1999 09:26:39 +0100
From: Laszlo Molnar <laszlo DOT molnar AT eth DOT ericsson DOT se>
To: Andris Pavenis <pavenis AT lanet DOT lv>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: egcs patch
Message-ID: <19990202092639.A21433@duna41>
References: <B0000069167 AT stargate DOT astr DOT lu DOT lv>; <19990201142609 DOT A20469 AT duna41> <B0000069247 AT stargate DOT astr DOT lu DOT lv>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.17i
In-Reply-To: <B0000069247@stargate.astr.lu.lv>; from Andris Pavenis on Mon, Feb 01, 1999 at 05:50:40PM +0200
Reply-To: djgpp-workers AT delorie DOT com

On Mon, Feb 01, 1999 at 05:50:40PM +0200, Andris Pavenis wrote:
> What we will do when gdb will support C++ exceptions. Are we going to put
> this information back then. Perhaps it's best not to touch eh_frame section
> too much not to break things we may need later.

AFAIK, gdb will not use information that is in section .eh_frame. It'll
use .debug_frame. And on djgpp there is no .eh_frame section in
linked executables, because it's merged into .data. So I think hacking
eh_frame won't cause problems.

Laszlo