Olivier Hainque wrote:
Michael Eager wrote:
I'll reverse-engineer the table unless I can find something
more descriptive than the comments in gcc or gdb.
FWIW, I did a similar exercise long ago and synthesized my
understanding in ada/raise-gcc.c, where the Ada personality routine
is impleme
Michael Eager wrote:
> I'll reverse-engineer the table unless I can find something
> more descriptive than the comments in gcc or gdb.
FWIW, I did a similar exercise long ago and synthesized my
understanding in ada/raise-gcc.c, where the Ada personality routine
is implemented.
Olivier
Hi,
On Sun, 17 May 2009, Michael Eager wrote:
> If the LSDA is only interpreted by the personality routine pointed to
> by the unwind table, then all that should be needed is to describe the
> the functionality of that routine.
Yep, that was what my confusion above was about, if the LSDA format
Michael Matz wrote:
Hi,
On Sun, 17 May 2009, Michael Eager wrote:
But the _format_ of the LSDA is not specified. It's really an
implementation detail of the compiler/language and doesn't have to be
agreed upon for mixing .o files from different compilers, as every
compilation unit can have
Hi,
On Sun, 17 May 2009, Michael Eager wrote:
> > But the _format_ of the LSDA is not specified. It's really an
> > implementation detail of the compiler/language and doesn't have to be
> > agreed upon for mixing .o files from different compilers, as every
> > compilation unit can have it's o
Michael Matz wrote:
Hi,
On Fri, 15 May 2009, Michael Eager wrote:
Is there any documentation on the contents of .eh_frame
and the augmentations used?
.eh_frame simply contains normal unwinding information, in DWARF2(34)
format, you're familiar with that :)
And nothing more, specifically i
Hi,
On Fri, 15 May 2009, Michael Eager wrote:
> Is there any documentation on the contents of .eh_frame
> and the augmentations used?
.eh_frame simply contains normal unwinding information, in DWARF2(34)
format, you're familiar with that :)
And nothing more, specifically it does _not_ contain
Michael Eager wrote:
> Ian Lance Taylor wrote:
>> Michael Eager writes:
>>
>>> Is there any documentation on the contents of .eh_frame
>>> and the augmentations used? IIRC, the data describes the
>>> try blocks and the catch handlers, but I'm looking for
>>> the gory details.
>>
>> I don't know o
Ian Lance Taylor wrote:
Michael Eager writes:
Is there any documentation on the contents of .eh_frame
and the augmentations used? IIRC, the data describes the
try blocks and the catch handlers, but I'm looking for
the gory details.
I don't know of any docs. Docs would be nice.
Here is the
Michael Eager writes:
> Is there any documentation on the contents of .eh_frame
> and the augmentations used? IIRC, the data describes the
> try blocks and the catch handlers, but I'm looking for
> the gory details.
I don't know of any docs. Docs would be nice.
Here is the comment from gcc/dw
Is there any documentation on the contents of .eh_frame
and the augmentations used? IIRC, the data describes the
try blocks and the catch handlers, but I'm looking for
the gory details.
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
11 matches
Mail list logo
