Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michal Ludvig <mludvig@suse.cz>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>,
	Andrew Cagney <ac131313@redhat.com>,
	Elena Zannoni <ezannoni@redhat.com>
Subject: Re: PING: [RFA] Runtime Dwarf2 CFI engine cleanup
Date: Thu, 27 Feb 2003 08:14:00 -0000	[thread overview]
Message-ID: <3E5DC8F6.9010301@suse.cz> (raw)
In-Reply-To: <20030226193829.GA20735@nevyn.them.org>

Daniel Jacobowitz wrote:
> In any case I am withdrawing my attempt to be helpful, since obviously
> I'm being pushy again instead of helpful.  Michal can go back to
> waiting for someone else's response since my "help" has obviously
> injured the entire process.

Thank you very much, anyway! You at least attempted to solve this issue.
Other "responsible" maintainers didn't bother to respond until you 
approved my patch. Then Andrew felt he should step in, revert your 
approval and say NO (why there doesn't come a *constructive* critique 
along with your no, Andrew?). And Elena - apparently the only one who 
could say yes - disappeared... Sigh.

I'm asking once again:
- Can I *at* *least* commit the dwarf2cfi.c part? Without the infcmd.c 
hook? I know it duplicates the solib cleaner logic, but is that a 
showstopper?
- Ad run_command() hook - would something like this be acceptable?

Index: config/i386/tm-x86-64linux.h
===================================================================
RCS file: /cvs/src/src/gdb/config/i386/tm-x86-64linux.h,v
retrieving revision 1.1
diff -u -p -r1.1 tm-x86-64linux.h
--- config/i386/tm-x86-64linux.h        1 Jul 2002 22:09:52 -0000       1.1
+++ config/i386/tm-x86-64linux.h        27 Feb 2003 08:02:50 -0000
@@ -33,4 +33,6 @@
  #define SVR4_SHARED_LIBS
  #include "solib.h"              /* Support for shared libraries. */

+#define DWARF2CFI_USED
+
  #endif /* #ifndef TM_X86_64LINUX_H */
Index: infcmd.c
===================================================================
RCS file: /cvs/src/src/gdb/infcmd.c,v
retrieving revision 1.54.6.2
diff -u -p -r1.54.6.2 infcmd.c
--- infcmd.c    25 Sep 2002 20:43:21 -0000      1.54.6.2
+++ infcmd.c    27 Feb 2003 08:02:50 -0000
@@ -390,6 +390,10 @@ Start it from the beginning? "))

    clear_breakpoint_hit_counts ();

+#if defined(DWARF2CFI_USED)
+  cleanup_cfi ();
+#endif
+
    /* Purge old solib objfiles. */
    objfile_purge_solibs ();

Every target that will use the CFI engine will just add one define to 
their tm.h. No need to link dwarf2cfi.o to all targets.

Comments?

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


  reply	other threads:[~2003-02-27  8:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06 12:55 Michal Ludvig
2003-02-03 16:23 ` Elena Zannoni
2003-02-10 12:30   ` Michal Ludvig
2003-02-26 15:35     ` PING: " Michal Ludvig
2003-02-26 15:47       ` Daniel Jacobowitz
2003-02-26 18:20         ` Andrew Cagney
2003-02-26 18:36           ` Daniel Jacobowitz
2003-02-26 19:32             ` Andrew Cagney
2003-02-26 19:38               ` Daniel Jacobowitz
2003-02-27  8:14                 ` Michal Ludvig [this message]
2003-02-27 10:15                   ` Michal Ludvig
2003-02-27 14:17                     ` Daniel Jacobowitz

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=3E5DC8F6.9010301@suse.cz \
    --to=mludvig@suse.cz \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=ezannoni@redhat.com \
    --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