Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jean-Rene Peulve <jr.peulve@wanadoo.fr>
Cc: gdb@sources.redhat.com
Subject: Re: Wrong address for static function in linux module
Date: Tue, 11 Apr 2006 13:38:00 -0000	[thread overview]
Message-ID: <20060411131142.GA21521@nevyn.them.org> (raw)
In-Reply-To: <6.1.0.6.0.20060411102654.00ad0710@pop.wanadoo.fr>

On Tue, Apr 11, 2006 at 11:01:13AM +0200, Jean-Rene Peulve wrote:
> Hi,
> I am debugging a linux module on a Coldfire and I encounter the following
> problem:
>  -functions which have the static attribut are always relocated at offset 0
>   of the .text section with the break command when the display command at 
>   the
>   right address disassemble the right static function.
>  -functions without the static attribut are relocated properly.
> 
>  I found out that the psymtab entry for a static function is relocated at 
>  the
>  right offset in the .text section when the symtab entry for the same 
>  function
>  is relocated at offset 0 of the .text section.
> 
>  To generate the target software, I use gcc 2.95.3
>  I was using gdb 5.2.1, then I fetch gdb-6.4.50.20060405 and get the same
>  problem.

This is normally supposed to be handled in
symfile_relocate_debug_section.  Are the bad functions really in
".text", or in another named text section?  Does the debug section
have proper relocations for that .debug_info entry (readelf -r)?


-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-11 13:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 13:33 Jean-Rene Peulve
2006-04-11 13:38 ` Daniel Jacobowitz [this message]
2006-04-11 13:45   ` Jean-Rene Peulve
2006-04-11 13:55     ` Daniel Jacobowitz
2006-04-11 14:41       ` Jean-Rene Peulve
2006-04-11 15:05         ` Daniel Jacobowitz
2006-04-12 11:38           ` Jean-Rene Peulve
2006-04-12 16:36           ` stabs vs dwarf (was: Re: Wrong address for static function in linux module ) David Taylor
2006-04-13  7:02             ` Mark Kettenis
2006-04-13  8:26               ` Eli Zaretskii

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=20060411131142.GA21521@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=jr.peulve@wanadoo.fr \
    /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