Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>
To: Michael Eager <eager@eagerm.com>,
	Michael Eager <eager@eagercon.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Joel Brobecker	<brobecker@adacore.com>
Cc: Vinod Kathail <vinodk@xilinx.com>,
	Vidhumouli Hunsigida	<vidhum@xilinx.com>,
	Nagaraju Mekala <nmekala@xilinx.com>
Subject: RE: [Patch, microblaze]: Add slr and shr regs and little-endian breakpoint
Date: Wed, 21 May 2014 12:55:00 -0000	[thread overview]
Message-ID: <5821f144-e431-4bee-9cd7-33971b5512a3@BN1AFFO11FD019.protection.gbl> (raw)
In-Reply-To: <537C5A25.9000003@eagerm.com>



-----Original Message-----
From: Michael Eager [mailto:eager@eagerm.com] 
Sent: Wednesday, May 21, 2014 1:18 PM
To: Ajit Kumar Agarwal; Michael Eager; gdb-patches@sourceware.org; Joel Brobecker
Cc: Vinod Kathail; Vidhumouli Hunsigida; Nagaraju Mekala
Subject: Re: [Patch, microblaze]: Add slr and shr regs and little-endian breakpoint

On 05/20/14 23:20, Ajit Kumar Agarwal wrote:
>
>
> On 05/20/14 09:25, Ajit Kumar Agarwal wrote:
>> Hello Joel:
>>
>> I have split the patches as you have recommended and the following is the first of the patch.
>>
>>    [Patch, microblaze]: Add slr and shr regs and little-endian 
>> breakpoint
>
>>> What is the relationship between adding slr/shr registers and little-endian breapoints?
>
> The shr/slr registers and little endian breakpoints are related as it 
> fixed the common problem of Packet Transfer error when connecting to the target remote host  through tar remote in gdb for microblaze.

>>>What "common" problem?  How do either of these changes related to a packet transfer error?

Here is the problem  description. The problem is related to process_g_packet where the buf_len > 2 * rsa->sizeof_g_packet and throwing the 
Error that 'g' packet message reply is too long. This is because the buf_len calculated in the init_remote_state function for microblaze target is based 
On the sizeof_g_packet and remote_packet_size and the memory_packet_config->size. The sizeof_g_packet is 236 because the number of reg num 
is 59 and 2* sizeof_g_packet comes to 472 .With shr and shl entry and the buf_len is 472. This does not match the greater than conditional statement
 and works fine. Without shr and shl entry,the sizeof_g_packets comes to 57*4 *2 = 456.  This doesn't match the criteria in the process_g_packet function
 leading to throwing of error message as  " 'g' packet message reply is too long".

This is happening when tar remote machine:1234 command is run in gdb.

>>>These changes don't appear related.  Split independent changes in to separate patches.

I will split the changes  and send the separate patch with shr and shl reg changes and the little endian breakpoint support.

Thanks & Regards
Ajit
-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077

  reply	other threads:[~2014-05-21 12:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 16:25 Ajit Kumar Agarwal
2014-05-20 21:14 ` Michael Eager
2014-05-21  6:20   ` Ajit Kumar Agarwal
2014-05-21  7:47     ` Michael Eager
2014-05-21 12:55       ` Ajit Kumar Agarwal [this message]
2014-05-21 13:45         ` Joel Brobecker
2014-05-22 17:58           ` Ajit Kumar Agarwal
2014-05-22 19:44             ` Michael Eager
2014-05-23  4:17               ` Ajit Kumar Agarwal
2014-05-23  5:57               ` Eli Zaretskii
2014-05-23  7:21                 ` Michael Eager
2014-05-23  7:35                   ` Eli Zaretskii
2014-05-21 13:41       ` Ajit Kumar Agarwal
2014-05-21 14:06         ` Pedro Alves

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=5821f144-e431-4bee-9cd7-33971b5512a3@BN1AFFO11FD019.protection.gbl \
    --to=ajit.kumar.agarwal@xilinx.com \
    --cc=brobecker@adacore.com \
    --cc=eager@eagercon.com \
    --cc=eager@eagerm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nmekala@xilinx.com \
    --cc=vidhum@xilinx.com \
    --cc=vinodk@xilinx.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