Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: Jean-Rene Peulve <jr.peulve@wanadoo.fr>
Cc: gdb@sources.redhat.com, Daniel Jacobowitz <dan@codesourcery.com>
Subject: Re: gdbserver for m68k-uclinux
Date: Tue, 09 May 2006 12:19:00 -0000	[thread overview]
Message-ID: <446069FB.40200@codesourcery.com> (raw)
In-Reply-To: <6.1.0.6.0.20060509114307.00a0e780@pop.wanadoo.fr>

Jean-Rene Peulve wrote:
> Hi Nathan,
> Oups: I resend this because the previous email was html and got bounced 
> by gdb@sources.redhat.com

Thanks for testing the patch out!

> I have been forced to change your patch to make it works.
> 
> 1)  missing return in server.c
The return you've added is unnecessary.

> 2) I also add an fprintf to stderr with the address of the text and data 
> section to allow the use of add-symbol_file command which requires these 
> address.
>   The response to qOffsets being hidden by gdb, I then can get it from 
> the target console or telnet.

Dan, I'll leave this change for you to decide.  I don't understand the usage 
here.  Why is it not necessary to know the text_end address in this case, for 
instance?

> +       if (the_target->read_offsets (&text, &data)) {
> +         sprintf (own_buf, "Text=%lX;Data=%lX;Bss=%lX",
> +                (long)text, (long)data, (long)data);
> +         return;
This return is not needed, why did you find it necessary?

> +       }
> +       else
> +         write_enn (own_buf);
> +
> +       return;
> +    }

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::         CodeSourcery
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk


  reply	other threads:[~2006-05-09 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08 16:57 Nathan Sidwell
2006-05-09 11:58 ` Jean-Rene Peulve
2006-05-09 12:19   ` Nathan Sidwell [this message]
2006-05-09 12:34     ` Jean-Rene Peulve
2006-05-09 12:39       ` Daniel Jacobowitz
2006-05-09 13:20 ` Daniel Jacobowitz
2006-05-09 14:13   ` Nathan Sidwell

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=446069FB.40200@codesourcery.com \
    --to=nathan@codesourcery.com \
    --cc=dan@codesourcery.com \
    --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