From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41042 invoked by alias); 24 Jun 2015 20:02:01 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 41029 invoked by uid 89); 24 Jun 2015 20:02:01 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,MIME_BASE64_BLANKS,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: ausxippc101.us.dell.com Received: from ausxippc101.us.dell.com (HELO ausxippc101.us.dell.com) (143.166.85.207) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (CAMELLIA256-SHA encrypted) ESMTPS; Wed, 24 Jun 2015 20:02:00 +0000 X-LoopCount0: from 10.175.216.249 From: To: Subject: Thread name in remote stub protocol Date: Wed, 24 Jun 2015 20:02:00 -0000 Message-ID: Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2015-06/txt/msg00082.txt.bz2 SeKAmXZlIGJlZW4gbG9va2luZyBpbnRvIEZyZWVCU0QgdGhyZWFkcyBzdXBw b3J0LCBhbmQgZ2Ric2VydmVyIHN1cHBvcnQuICBGcmVlQlNEIGhhcyB0aGUg bm90aW9uIG9mIHRocmVhZCBuYW1lcywgYW5kIGl04oCZcyBlYXN5IGVub3Vn aCB0byBtYWtlIG5hdGl2ZSBHREIgaGFuZGxlIHRoYXQuICBnZGJzZXJ2ZXIg aXMgYW5vdGhlciBtYXR0ZXIuICBJIGxvb2tlZCBhbGwgb3ZlciB0aGUgdmFy aW91cyB0aHJlYWQgcmVsYXRlZCBtZXNzYWdlcywgYW5kIHdoaWxlIHRoZXJl IGFyZSBhIGJ1bmNoIG9mIG9wcG9ydHVuaXRpZXMgZm9yIHRoaXMgdG8gYmUg aGFuZGxlZCwgaXQgaXNu4oCZdCByZWFsbHkgdGhlcmUuDQoNCkkgY2FuIHNl ZSB0aGUgZGVwcmVjYXRlZCBxUCBwYWNrZXQgdGhhdCBjYXJyaWVzIGEg4oCc c2hvcnRuYW1l4oCdLiAgVGhhdCBsb29rcyBpbnRlcmVzdGluZywgYnV0IHdo aWxlIHRoZSBwYWNrZXQgcGFyc2luZyBpcyB0aGVyZSwgaXQgaXNu4oCZdCBj bGVhciB0aGUgdmFsdWUgZ29lcyBhbnl3aGVyZS4gIFNpbWlsYXJseSwgdGhl cmUgaXMgcVRocmVhZEV4dHJhSW5mbyB3aGljaCBhbGxvd3MgZm9yIGEgZnJl ZSBmb3JtIHN0cmluZy4gIEFuZCB0aGVyZSBpcyBxWGZlcjp0aHJlYWRzLCBi dXQgdGhhdCBjYXJyaWVzIG9ubHkgYW4gSUQgYW5kIGEgY29yZSBudW1iZXIu ICBBbmQgbm9uZSBvZiB0aGVzZSBzZWVtIHRvIGJlIGNsZWFubHkgdGllZCB0 byB0aGUgbWFpbiBnZGIgdGhyZWFkIG5hbWUgbWFjaGluZXJ5Lg0KDQpXaGF0 IHRvIGRvIGFib3V0IHRoaXM/ICBDb3VsZCBxWGZlcjp0aHJlYWRzIGJlIGV4 dGVuZGVkIHRvIGFkZCBhIHRocmVhZCBuYW1lIGZpZWxkPyAgT3Igc2hvdWxk IEkganVzdCB1c2UgdGhlIFRocmVhZEV4dHJhSW5mbyBtZWNoYW5pc20gYW5k IGlnbm9yZSB0aGUgZmFjdCB0aGF0IGl0IGNvbnZleXMgZXh0cmEgaW5mbyBy YXRoZXIgdGhhbiB0aGUgdGhyZWFkIG5hbWU/DQoNCglwYXVsDQo= >From gdb-return-44478-listarch-gdb=sources.redhat.com@sourceware.org Thu Jun 25 01:22:47 2015 Return-Path: Delivered-To: listarch-gdb@sources.redhat.com Received: (qmail 26431 invoked by alias); 25 Jun 2015 01:22:47 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Delivered-To: mailing list gdb@sourceware.org Received: (qmail 26420 invoked by uid 89); 25 Jun 2015 01:22:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ig0-f172.google.com Received: from mail-ig0-f172.google.com (HELO mail-ig0-f172.google.com) (209.85.213.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 25 Jun 2015 01:22:45 +0000 Received: by igblr2 with SMTP id lr2so45725229igb.0 for ; Wed, 24 Jun 2015 18:22:43 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.117.66 with SMTP id kc2mr767840igb.31.1435195363421; Wed, 24 Jun 2015 18:22:43 -0700 (PDT) Received: by 10.36.12.200 with HTTP; Wed, 24 Jun 2015 18:22:43 -0700 (PDT) Date: Thu, 25 Jun 2015 01:22:00 -0000 Message-ID: Subject: Why gdb/gdbserver handler breakpoint on gdb client side (ARM)? From: Fei Ding To: "gdb@sourceware.org" Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-06/txt/msg00083.txt.bz2 Content-length: 440 Hi. Recently I am working on debugging a bug of gdb/gdbserver when setting breakpoints on ARM devices. I found that, gdb-client nearly do nothing about it when we use gdb/gdbserver on x86 platform, gdbserver do the dirty work in fact, including generate INT 3 instruction, read, save, and write memory, etc... But for ARM, this work is done on the gdb-client side, which is opposed to x86 case. Anyone know why? Or any thoughts? Thanks.