Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro_alves@portugalmail.pt>
To: gdb-patches@sourceware.org,  insight@sourceware.org
Subject: Re: syms_from_objfile() warnings and win32-nat.c IO redirection   (Was: suppress annoying warnings about cygwin1.dbg)
Date: Mon, 29 Oct 2007 22:54:00 -0000	[thread overview]
Message-ID: <47266460.10204@portugalmail.pt> (raw)
In-Reply-To: <20071029123318.GA16009@caradoc.them.org>

I'm a bit puzzled, since I've just found out that:

strip --strip-debug ${dest} -o ${stripped_file}
strip --only-keep-debug main.exe -o ${debug_file}
objcopy --add-gnu-debuglink=${debug_file} ${stripped_file} ${dest}

... currently plays nicelly in PE/coff + stabs+.  The
CONTENTS | ALLOC sections simply get
the CONTENTS dropped, thus it seems that gdb
doesn't need any fixing after all.

>objdump.exe -h main.exe

main.exe:     file format pei-i386

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
   0 .text         000003a0  00401000  00401000  00000400  2**4
                   CONTENTS, ALLOC, LOAD, READONLY, CODE
   1 .data         00100000  00402000  00402000  00000800  2**4
                   CONTENTS, ALLOC, LOAD, DATA
   2 .bss          00000040  00502000  00502000  00000000  2**4
                   ALLOC
   3 .idata        00000170  00503000  00503000  00100800  2**2
                   CONTENTS, ALLOC, LOAD, DATA
   4 .gnu_debuglink 00000014  00504000  00504000  00100a00  2**2
                   CONTENTS, READONLY, DEBUGGING

>objdump.exe -h main.exe.dbg

main.exe.dbg:     file format pei-i386

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
   0 .text         000003a0  00401000  00401000  00000000  2**4
                   ALLOC, LOAD, READONLY, CODE
   1 .data         00100000  00402000  00402000  00000000  2**4
                   ALLOC, LOAD, DATA
   2 .bss          00000040  00502000  00502000  00000000  2**4
                   ALLOC
   3 .idata        00000170  00503000  00503000  00000000  2**2
                   ALLOC, LOAD, DATA
   4 .stab         0000c630  00504000  00504000  00000268  2**2
                   CONTENTS, READONLY, DEBUGGING, EXCLUDE
   5 .stabstr      0004e99f  00511000  00511000  0000ca68  2**0
                   CONTENTS, READONLY, DEBUGGING, EXCLUDE


Chris, Brian, would it be possible to instead fix the
cygwin1.dbg generation to do something similar to
the above recipe?

I'm posting a few patches to enable sepdebug.exp and
sepsymtab.exp testing on Cygwin.

I've also locally hacked shreloc.exp to generate seperate
debug info to test shared objects, and relocation, as
that isn't currently tested by sepdebug.exp.  It worked
fine.

This means the patches upthread are withdrawn
for now.

Cheers,
Pedro Alves




  reply	other threads:[~2007-10-29 22:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46262D3A.8B1A0D15@dessent.net>
     [not found] ` <20070418150137.GA7338@trixie.casa.cgf.cx>
     [not found]   ` <46263710.D9755DAD@dessent.net>
     [not found]     ` <462639F3.FBCF4675@dessent.net>
     [not found]       ` <46264A56.BA86EED7@dessent.net>
2007-05-02 15:19         ` [patch ping] suppress annoying warnings about cygwin1.dbg Brian Dessent
2007-06-25 23:20           ` [patch ping^2] " Brian Dessent
2007-06-25 23:40             ` Pedro Alves
2007-06-25 23:52               ` Daniel Jacobowitz
2007-06-26  0:59                 ` Brian Dessent
2007-06-26  7:37                   ` Daniel Jacobowitz
2007-06-28  6:11                 ` syms_from_objfile() warnings and win32-nat.c IO redirection (Was: suppress annoying warnings about cygwin1.dbg) Brian Dessent
2007-06-28 12:44                   ` Daniel Jacobowitz
2007-10-11 20:26                     ` Daniel Jacobowitz
2007-10-13  0:09                       ` Brian Dessent
2007-10-13  1:44                         ` Pedro Alves
2007-10-13  2:49                           ` Brian Dessent
2007-10-13  3:33                             ` Pedro Alves
2007-10-13  6:03                               ` Brian Dessent
2007-10-24 19:06                           ` Daniel Jacobowitz
2007-10-29  3:06                             ` Pedro Alves
2007-10-29 12:33                               ` Pedro Alves
2007-10-29 12:57                                 ` Daniel Jacobowitz
2007-10-29 22:54                                   ` Pedro Alves [this message]
2007-10-30  4:05                                     ` Christopher Faylor
2007-10-30  9:02                                       ` Pedro Alves
2007-10-30  1:27                                   ` Christopher Faylor
2007-11-08 23:56                                     ` Pedro Alves
2007-11-09  1:35                                       ` Pedro Alves
2007-11-09 13:34                                         ` Christopher Faylor
2007-11-09 13:59                                           ` Pedro Alves
2007-11-09 13:59                                           ` Daniel Jacobowitz

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=47266460.10204@portugalmail.pt \
    --to=pedro_alves@portugalmail.pt \
    --cc=gdb-patches@sourceware.org \
    --cc=insight@sourceware.org \
    /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