Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@cygnus.com>
To: Joel Brobecker <brobecker@act-europe.fr>
Cc: Elena Zannoni <ezannoni@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch] Fix uninitialized section index internal error
Date: Thu, 28 Jun 2001 20:17:00 -0000	[thread overview]
Message-ID: <15163.62314.851953.480908@kwikemart.cygnus.com> (raw)
In-Reply-To: <20010628142306.C28801@act-europe.fr>

Joel Brobecker writes:
 > > Sorry, but we are trying to move away from having gdb knowing that
 > > some sections are special. Adding a new SECT_OFF_SBSS macro, would not
 > > be in line with that. Would you mind just doing that bit I suggested?
 > > That would solve your immediate problem, right?
 > 
 > Elena,
 > 
 >   I implemented your suggestion, but I stumbled accross another problem
 > that puzzled me.
 > 
 >   the program that I provided as an example to reproduce the problem
 > does in fact contain some symbols located in the .bss section ('end' for
 > instance), but gdb could had not located it. I verified this by using nm:
 > 
 > List of symbols in the .bss section:
 > <<
 > % nm -B mach | grep ' B '
 > 0x00000140000160 B .bss
 > 0x00000140000160 B _ebss
 > 0x00000140000160 B _end
 > 0x00000140000160 B end
 > >>
 > 
 > List of symbols in the .sbss section:
 > <<
 > % nm -B mach | grep ' S '
 > 0x00000140000140 S .sbss
 > 0x00000140000140 S __Argc
 > 0x00000140000158 S __Argv
 > 0x00000140000150 S _auxv
 > 0x00000140000140 S _fbss
 > 0x00000140000148 S _ldr_present
 > >>
 > 
 > Unfortunately, I don't have enough time to persue this right now. In
 > think my changes improve a bit the current situation, but do not fix all
 > problems, so I'm not sure they should be submitted yet.

Hmm, I think that if your changes are an improvement, and don't break
anything else, it is worth including them in the sources, so they
don't get lost. 

 > 
 > I'll look into why gdb can not find this .bss section when I have more time
 > available.
 > 

Thanks for doing this.

Elena


 > -- 
 > Joel
 > 


  reply	other threads:[~2001-06-28 20:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-10 14:40 Joel Brobecker
2001-06-12 14:18 ` Elena Zannoni
2001-06-14 23:40   ` Joel Brobecker
2001-06-27 22:32     ` Elena Zannoni
2001-06-28  5:23       ` Joel Brobecker
2001-06-28 20:17         ` Elena Zannoni [this message]
2001-11-06  7:40     ` Joel Brobecker

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=15163.62314.851953.480908@kwikemart.cygnus.com \
    --to=ezannoni@cygnus.com \
    --cc=brobecker@act-europe.fr \
    --cc=gdb-patches@sources.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