Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Richard Henderson <rth@redhat.com>
Cc: gdb-patches@gcc.gnu.org
Subject: Re: [rfc] conditional 128-bit long double
Date: Sun, 07 Mar 2004 20:19:00 -0000	[thread overview]
Message-ID: <404B83BC.1080100@gnu.org> (raw)
In-Reply-To: <20040307080658.GA18878@redhat.com>

> The only thing that would be better is if gdb could look up long double
> in the debug info:

GDB needs to come up in a sane state without debug info - stripped 
executable or even:

$ gdb
(gdb) print (long double) 1 * 2

so you can't rely on debug info.

> but I have no idea if one could even think doing such a thing in gdb.
> I expect to *never* have to handle applications with mismatched types,
> as I'm planning to bump the libc version number before this is over.

Won't you also want to brand the executable and object file?  Without 
that it will be too wasy to link the wrong object file into the wrong 
executable.

GDB handles ABI variants with OSABI sniffers that key off the brand.

Andrew



WARNING: multiple messages have this Message-ID
From: Andrew Cagney <cagney@gnu.org>
To: Richard Henderson <rth@redhat.com>
Cc: gdb-patches@gcc.gnu.org
Subject: Re: [rfc] conditional 128-bit long double
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <404B83BC.1080100@gnu.org> (raw)
Message-ID: <20040319000900.3bO-w_UUPteNLTFGhop2_9Yv4RHYPArtgP-mV9abOfE@z> (raw)
In-Reply-To: <20040307080658.GA18878@redhat.com>

> The only thing that would be better is if gdb could look up long double
> in the debug info:

GDB needs to come up in a sane state without debug info - stripped 
executable or even:

$ gdb
(gdb) print (long double) 1 * 2

so you can't rely on debug info.

> but I have no idea if one could even think doing such a thing in gdb.
> I expect to *never* have to handle applications with mismatched types,
> as I'm planning to bump the libc version number before this is over.

Won't you also want to brand the executable and object file?  Without 
that it will be too wasy to link the wrong object file into the wrong 
executable.

GDB handles ABI variants with OSABI sniffers that key off the brand.

Andrew



  parent reply	other threads:[~2004-03-07 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Richard Henderson
2004-03-07  8:07 ` Richard Henderson
2004-03-07 20:19 ` Andrew Cagney [this message]
2004-03-19  0:09   ` 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=404B83BC.1080100@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@gcc.gnu.org \
    --cc=rth@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