This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Fix unwinding through SA_ONSTACK signal frames on IA-64


>>>>> On Fri, 19 Dec 2003 13:44:28 -0500, Jakub Jelinek <jakub@redhat.com> said:

  Jakub> Your libunwind does it too, though not at the time you pass
  Jakub> the alternate stack crossing signal frame, but when
  Jakub> installing the context.  But that can very well be right in
  Jakub> the frame above it, at which point the same space is needed
  Jakub> in both implementations.

  Jakub> Also, the application has no control about the RSE engine,
  Jakub> which can decide any time to flush all or almost all
  Jakub> registers to backing store at its discretion.

You may not be able to throw an exception (that's hard in general),
but at least you could get a stack trace with libunwind.

  Jakub> Any application which doesn't have enough space for its dirty
  Jakub> registers in its current backing store is seriously broken
  Jakub> IMHO.

Perhaps, but it certainly can happen easily with out-of-hand
recursion.  Some applications (especially ones with built-in
interpreters) may want to guard against that and at least provide a
graceful exit.

	--david


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]