Bug 5886 - frysk.stack.ErrorFrame class
Summary: frysk.stack.ErrorFrame class
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 5876
  Show dependency tree / graph
 
Reported: 2008-03-05 17:10 UTC by Andrew Cagney
Modified: 2008-04-01 18:06 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2008-03-05 17:10:36 UTC 
If the unwind attempt fails with an error then an ErrorFrame class would be used
to terminate the stack chain (with frame id == 0).

This way, a back-trace could contain an additional error frame vis:

   (fhpd) where
   #0 foo
   #1 bar
   #2 <<error: invalid memory address at 0>>
   (fhpd)

making it easier to differentiate between a bad back-trace and a properly
terminated stack.  In addition, if the user should want, they can even examine
that frame.