Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michal Ludvig <mludvig@suse.cz>
To: GDB Patches <gdb-patches@sources.redhat.com>
Subject: [RFA] Debug info detection.
Date: Thu, 06 Mar 2003 23:06:00 -0000	[thread overview]
Message-ID: <3E67D471.3040100@suse.cz> (raw)

[-- Attachment #1: Type: text/plain, Size: 431 bytes --]

Hi all,
The attached patch adds new function cfi_have_unwind_info() that I'll 
use for detection, whether a given function has a dwarf2 unwind info 
(from .eh_frame or .debug_frame) or not. I'll use it in the upcomming 
x86_64_frame_p() to detect which set of unwind functions should be 
returned for a given frame.

OK to commit?

Michal Ludvig
-- 
* SuSE CR, s.r.o     * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz

[-- Attachment #2: cfi-haveinfo-1.diff --]
[-- Type: text/plain, Size: 1451 bytes --]

2003-03-06  Michal Ludvig  <mludvig@suse.cz>

	* dwarf2cfi.c (cfi_have_unwind_info): New function.
	* dwarf2cfi.h (cfi_have_unwind_info): New prototype.

Index: dwarf2cfi.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2cfi.c,v
retrieving revision 1.31
diff -u -p -r1.31 dwarf2cfi.c
--- dwarf2cfi.c	10 Feb 2003 11:50:20 -0000	1.31
+++ dwarf2cfi.c	6 Mar 2003 22:57:56 -0000
@@ -835,6 +835,12 @@ frame_state_for (struct context *context
 		       fde->data + fde->data_length, context, fs);
 }
 
+struct fde_unit *
+cfi_have_unwind_info (CORE_ADDR pc)
+{
+  return get_fde_for_addr (pc);
+}
+
 static void
 get_reg (char *reg, struct context *context, int regnum)
 {
Index: dwarf2cfi.h
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2cfi.h,v
retrieving revision 1.4
diff -u -p -r1.4 dwarf2cfi.h
--- dwarf2cfi.h	9 Dec 2002 02:04:16 -0000	1.4
+++ dwarf2cfi.h	6 Mar 2003 22:57:56 -0000
@@ -75,6 +75,9 @@ void cfi_init_extra_frame_info (int from
 /* Obtain return address of the frame.  */
 CORE_ADDR cfi_get_ra (struct frame_info *fi);
 
+/* Check if there is an unwind info for a given PC.  */
+struct fde_unit *cfi_have_unwind_info (CORE_ADDR pc);
+
 /* Find register number REGNUM relative to FRAME and put its
    (raw) contents in *RAW_BUFFER.  Set *OPTIMIZED if the variable
    was optimized out (and thus can't be fetched).  If the variable

             reply	other threads:[~2003-03-06 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 23:06 Michal Ludvig [this message]
2003-03-07 15:25 ` Andrew Cagney
2003-03-07 15:48   ` Michal Ludvig
2003-03-07 16:32     ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E67D471.3040100@suse.cz \
    --to=mludvig@suse.cz \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox