public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: ezannoni@redhat.com, kettenis@chello.nl
Cc: gdb@sources.redhat.com
Subject: Re: SOFUN_ADDRESS_MAYBE_MISSING
Date: Wed, 15 Oct 2003 18:44:00 -0000	[thread overview]
Message-ID: <200310151844.h9FIiLUJ024257@duracef.shout.net> (raw)

eza> I tried *deleting* the definition of SOFUN_ADDRESS_.. in
eza> config/i386/tm-linux.h, and I ran the testsuite both on a stabs platform
eza> (RH 7.3) and a dwarf2 platform (RH 9) and found no differences in the
eza> testsuite results, before and after the change (of course there are
eza> the usual differences between the stabs and the dwarf2 runs).

BTW, you might already know this, but you can run stabs+ on RH 9 with:

  runtest ... --target_board unix/gdb:debug_flags=-gstabs+

I don't know the right incantation for doing this at the
"make check" level.

eza> This would require to increase the size of a minsym in all
eza> cases, by making this unconditional:

My data point is that minsym size is not important: about 0.3 megabytes
out of 80 megabytes with "gdb --readnow gdb".  Dunno about the normal
case without "--readnow" but I wouldn't worry about increasing the
size of a minsym if that helps fix a problem.

My two superficial observations,

Michael C

             reply	other threads:[~2003-10-15 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 18:44 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-06 12:42 SOFUN_ADDRESS_MAYBE_MISSING Mark Kettenis
2003-10-06 16:44 ` SOFUN_ADDRESS_MAYBE_MISSING Kevin Buettner
2003-10-07 16:44   ` SOFUN_ADDRESS_MAYBE_MISSING Jim Blandy
2003-10-07  4:24 ` SOFUN_ADDRESS_MAYBE_MISSING Jim Blandy
2003-10-15 18:21 ` SOFUN_ADDRESS_MAYBE_MISSING Elena Zannoni
2003-10-16 19:49   ` SOFUN_ADDRESS_MAYBE_MISSING 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=200310151844.h9FIiLUJ024257@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).