From: Daniel Jacobowitz <drow@false.org>
To: Sergei Poselenov <sposelenov@emcraft.com>
Cc: gdb@sourceware.org
Subject: Re: [rfc / remote protocol] ELF segment based qOffsets
Date: Mon, 17 Dec 2007 22:55:00 -0000 [thread overview]
Message-ID: <20071217225456.GA24192@caradoc.them.org> (raw)
In-Reply-To: <47625A95.7080203@emcraft.com>
On Fri, Dec 14, 2007 at 01:27:33PM +0300, Sergei Poselenov wrote:
> You see, the warnings are caused by the fact that the segment 01 has
> address/size values which wraps to 0 in the following 'if' condition
> introduced by the $subj in elfread.c, elf_symfile_segments():
> ...
> && vma < segments[j]->p_vaddr + segments[j]->p_memsz)
Drat. Yes, this just seems like a bug. I'll try to fix it later.
> The place above is trivial to fix, but I wonder will be any
> other consequences to the remote debugging of such kind of
> images? (I can't try this at the moment)
I don't think there should be any problems. There would be a little
trouble debugging code from those sections if the image was relocated
(qOffsets response), but yours shouldn't be; it goes at the address in
the ELF file.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-17 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 10:29 Sergei Poselenov
2007-12-17 22:55 ` Daniel Jacobowitz [this message]
2007-12-19 15:45 ` Sergei Poselenov
2007-12-19 16:20 ` Sergei Poselenov
-- strict thread matches above, loose matches on Subject: below --
2007-05-09 19:12 Daniel Jacobowitz
2007-05-09 19:47 ` Eli Zaretskii
2007-05-19 17:38 ` Pedro Alves
2007-06-18 15:48 ` 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=20071217225456.GA24192@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=sposelenov@emcraft.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