Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Artifical dwarf2 debug info
Date: Mon, 16 Dec 2002 07:49:00 -0000	[thread overview]
Message-ID: <20021216152934.GA13042@nevyn.them.org> (raw)
In-Reply-To: <3DFDDBFA.4080406@suse.cz>

On Mon, Dec 16, 2002 at 02:58:18PM +0100, Michal Ludvig wrote:
> Daniel Jacobowitz wrote:
> >On Sun, Dec 15, 2002 at 01:48:12AM +0100, Michal Ludvig wrote:
> >
> >>this long patch provides a fix for a very annoying fact, that GDB on 
> >>x86-64 can't do backtraces from hand-optimized assembler functions (that 
> >>applies for example to glibc's memset, str*, etc as well as to syscall 
> >>wrappers).
> >
> >Workaround, really - just for some particular functions...
> 
> Yes, but still better than nothing ;-)

Yeah.

> OK, the attached patch has a modified gdbarch.sh and regenerated 
> gdbarch.[ch].
> 
> I've also put a description into gdbint.texinfo

OK, Eli will have to approve that part.

> >>OK to commit to branch and mainline?
> >
> >I do not believe this is appropriate for the branch, at least until
> >it's sat on mainline without causing problems for some time.
> 
> It shouldn't cause any problems because all the machinery is invoked if 
> and only if the target allowed it, and then if a FDE isn't found for a 
> particular function. Typically only two or three times on x86-64 and 
> zero times on other archs.
> 
> Can I put it at least to mainline?

A little way to go yet.  Please don't just export things from
dwarf2cfi:

> +/* Common Information Entry - holds information that is shared among many
> +   Frame Descriptors.  */
> +struct cie_unit

This is fine for now.

> +/* Frame Description Entry.  */
> +struct fde_unit
> +{

So's this.

> +struct fde_array
> +{
> +  struct fde_unit **array;
> +  int elems;
> +  int array_size;
> +};
> +
> +extern struct cie_unit *cie_chunks;
> +extern struct fde_array fde_chunks;
> +

But these aren't.  Add a function to link a new FDE or CIE, please.

> +struct cie_unit *cie_unit_alloc (void);
> +struct fde_unit *fde_unit_alloc (void);

These make sense...

> +void fde_chunks_need_space (void);
> +int compare_fde_unit (const void *a, const void *b);

But these aren't necessary if you add said function.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-12-16 15:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-14 17:31 Michal Ludvig
2002-12-14 22:53 ` Eli Zaretskii
2002-12-15 11:03 ` Daniel Jacobowitz
2002-12-16  7:28   ` Michal Ludvig
2002-12-16  7:49     ` Daniel Jacobowitz [this message]
2002-12-16  9:27       ` Michal Ludvig
2002-12-16  9:54         ` Daniel Jacobowitz
2002-12-16 10:38         ` Eli Zaretskii
2002-12-20  8:43           ` Michal Ludvig
2002-12-20 10:51             ` Eli Zaretskii
2002-12-16  9:25 ` Andrew Cagney
2002-12-16  9:40   ` Daniel Jacobowitz
2002-12-16 10:04     ` Andrew Cagney
2002-12-16 10:17       ` Daniel Jacobowitz
2002-12-16 10:56         ` Andrew Cagney
2002-12-16 11:13           ` Daniel Jacobowitz
2002-12-16 11:34             ` Andrew Cagney
2002-12-16 11:57               ` Daniel Jacobowitz
2002-12-16 12:10                 ` Andrew Cagney
2002-12-16 12:42                   ` Daniel Jacobowitz
2002-12-17  6:23                     ` Michal Ludvig
2002-12-17  6:28                       ` Andrew Cagney
2002-12-17  8:42                         ` Daniel Jacobowitz
2002-12-18  4:39                           ` Andrew Cagney
2002-12-18 10:05                             ` Daniel Jacobowitz
2003-01-02 20:54                               ` Andrew Cagney
2003-01-02 21:19                                 ` Daniel Jacobowitz
2003-01-02 23:05                                   ` Andrew Cagney
2003-01-02 23:27                                     ` Daniel Jacobowitz
2003-01-03  0:28                                       ` Andrew Cagney
2002-12-16  9:46   ` Michal Ludvig
2002-12-16  9:57     ` Andrew Cagney
2002-12-16 10:01       ` Michal Ludvig

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=20021216152934.GA13042@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mludvig@suse.cz \
    /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