Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Andreas Schwab <schwab@suse.de>, gdb-patches@sourceware.org
Subject: Re: [patch] Fix a glitch in debugging 32-bit process with 64-bit GDB.
Date: Mon, 15 Dec 2008 08:59:00 -0000	[thread overview]
Message-ID: <20081215085833.GL6866@adacore.com> (raw)
In-Reply-To: <8ac60eac0812131017l6eec4bf9r1a9fedf3e68bc6bb@mail.gmail.com>

> > It seems to me that this should work without negative effect
> > (we have to be a little careful because there is a 64bit stabs
> > extension on Tru64).
> 
> AFAICT, Tru64 goes through ECOFF reader in mdebugread.c, and so
> wouldn't be affected by a change to dbxread.c

You're probably right. I'm a little fuzzy now about what each module
does and I'm a little tied up to investigate further. Regardless,
I think that this won't affect Tru64 anyway.

> 2008-12-12  Paul Pluzhnikov  <ppluzhnikov@google.com>
> 
>         * dbxread.c (read_ofile_symtab): Sign-extend 32-bit N_LSYM and
>         N_PSYM STABS values for 64-bit GDB.

This looks reasonable to me, but I'd really like to have a more detailed
comment:

> +	  if (sizeof (nlist.n_value) > 4
> +	      && (type == N_LSYM || type == N_PSYM))
> +	    /* These are very likely to be 32-bit negative.
> +	       Sign-extend them for 64-bit GDB.  */
> +	    nlist.n_value = (nlist.n_value ^ 0x80000000) - 0x80000000;

In particular:

  . Why are we testing the size of nlist.n_value? (to detect that we
    are using a 64bit debugger)
  . You mention that this is very likely to be 32-bit negative, but
    offsets on some platforms may be positive.

I'd like to see the comment detail a little the situation that we are
trying to solve (64bit gdb debugging a 32bit app). Just as a starting
point, I suggest for instance:

  if (sizeof (nlist.n_value) > 4)
    /* We are a 64bit debugger debugging a 32bit program.
       We have to be a little careful with the n_value in the case
       of N_LSYM and N_PSYM entries, because they are signed offsets
       that we actually read as an unsigned 32bit value. This is
       not a problem with 32bit debuggers where negative values end
       up being interpreted correctly.  But we need to sign-extend
       the sign bit on 64bit debuggers.  Otherwise, we'll end up
       interpreting negative values as very large positive values...  */
    if (type == N_LSYM || type == N_PSYM)
      nlist.n_value = (nlist.n_value ^ 0x80000000) - 0x80000000;

-- 
Joel


  reply	other threads:[~2008-12-15  8:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09  1:33 Paul Pluzhnikov
2008-12-09  2:08 ` Daniel Jacobowitz
2008-12-09  2:43   ` Paul Pluzhnikov
2008-12-09 11:30     ` Peter Schauer
2008-12-09 13:34     ` Daniel Jacobowitz
2008-12-10 11:14       ` Joel Brobecker
2008-12-10 15:59         ` Paul Pluzhnikov
2008-12-10 23:21           ` Paul Pluzhnikov
2008-12-11  8:57             ` Andreas Schwab
     [not found]               ` <8ac60eac0812111601v20566268h6f7977c71e5b8a8f@mail.gmail.com>
2008-12-12  0:11                 ` Paul Pluzhnikov
2008-12-13 16:02                   ` Joel Brobecker
2008-12-13 18:18                     ` Paul Pluzhnikov
2008-12-15  8:59                       ` Joel Brobecker [this message]
2008-12-15 21:47                         ` Paul Pluzhnikov
2008-12-16  4:48                           ` Joel Brobecker
2008-12-11  9:21             ` Mark Kettenis

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=20081215085833.GL6866@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ppluzhnikov@google.com \
    --cc=schwab@suse.de \
    /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