diff options
| author | Jim Kingdon <jkingdon@engr.sgi.com> | 1993-10-15 19:37:29 +0000 |
|---|---|---|
| committer | Jim Kingdon <jkingdon@engr.sgi.com> | 1993-10-15 19:37:29 +0000 |
| commit | 78cab901b0926948ddb520df9f10b96cfa0faef1 (patch) | |
| tree | 9055e543e4f66d8147fb41e1e8d6602a25070dc9 /gdb/breakpoint.h | |
| parent | d699eb21249adf4d9e3e52be62d98b9b54ca362b (diff) | |
| download | gdb-78cab901b0926948ddb520df9f10b96cfa0faef1.zip gdb-78cab901b0926948ddb520df9f10b96cfa0faef1.tar.gz gdb-78cab901b0926948ddb520df9f10b96cfa0faef1.tar.bz2 | |
* Move comments on bypassing call dummy breakpoint from stack.c
to breakpoint.h.
Diffstat (limited to 'gdb/breakpoint.h')
| -rw-r--r-- | gdb/breakpoint.h | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/gdb/breakpoint.h b/gdb/breakpoint.h index 589915d..2bebe3e 100644 --- a/gdb/breakpoint.h +++ b/gdb/breakpoint.h @@ -50,6 +50,12 @@ enum bptype { bp_step_resume, /* The breakpoint at the end of a call dummy. */ + /* FIXME: What if the function we are calling longjmp()s out of the + call, or the user gets out with the "return" command? We currently + have no way of cleaning up the breakpoint in these (obscure) situations. + (Probably can solve this by noticing longjmp, "return", etc., it's + similar to noticing when a watchpoint on a local variable goes out + of scope (with hardware support for watchpoints)). */ bp_call_dummy }; |