Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Alexander Larsson <alexl@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Final separate debug info patch
Date: Mon, 18 Nov 2002 23:47:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0211190244510.10486-100000@devserv.devel.redhat.com> (raw)
In-Reply-To: <vt2wunajgl9.fsf@zenia.red-bean.com>

On 19 Nov 2002, Jim Blandy wrote:

> 
> It looks like the stripping process may break some executables.  If $D
> is the top directory of a current GDB source tree, try this:
> 
> $ g++ --version
> g++ (GCC) 3.3 20020820 (experimental)
> Copyright (C) 2002 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> $ g++ -g $D/gdb/testsuite/gdb.c++/try_catch.cc -o try_catch
> $ ./try_catch
> $ /home/jimb/elfutils/bin/strip -f try_catch.separate-debug try_catch
> $ ./try_catch
> Segmentation fault
> $ 

This doesn't happen for me with gdb from cvs HEAD and gcc (GCC) 3.2 
20020903 (Red Hat Linux 8.0 3.2-7). Does it happen if you just run strip 
without the -f flag? It might well be a bug in the new strip command.

> So the effect is to:
> - run all the tests once with separate debug info, and then
> - run all the tests again with the normal debug info arrangement.
> 
> This makes it easy to see if the patch has any effect on the tests.

Thats cool.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
                   alexl@redhat.com    alla@lysator.liu.se 
He's a superhumanly strong alcoholic grifter who hides his scarred face behind 
a mask. She's a time-travelling antique-collecting Hell's Angel with a knack 
for trouble. They fight crime! 


  parent reply	other threads:[~2002-11-19  7:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09  1:54 Alexander Larsson
2002-11-18 21:20 ` Jim Blandy
2002-11-18 21:32   ` Daniel Jacobowitz
2002-11-19  3:53     ` Jim Blandy
2002-11-18 23:47   ` Alexander Larsson [this message]
2002-11-19  3:38     ` Jim Blandy
2002-11-19  3:57       ` Alexander Larsson
2002-11-19 12:47         ` Alexander Larsson
2002-11-20 21:43           ` Jim Blandy
2002-11-20 23:35             ` Alexander Larsson
2002-11-19  5:00   ` Jim Blandy
2002-11-18 22:11 ` Jim Blandy
2002-11-18 23:51   ` Alexander Larsson
2002-11-19  0:02     ` Ulrich Drepper
2002-11-19  3:47       ` Jim Blandy
2002-11-19  3:53         ` Alexander Larsson
2002-11-19  4:38           ` Jim Blandy
2002-11-24 20:28 ` Jim Blandy
2002-11-25  5:37   ` Alexander Larsson
2002-11-25  9:44     ` Jim Blandy

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=Pine.LNX.4.44.0211190244510.10486-100000@devserv.devel.redhat.com \
    --to=alexl@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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