From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82326 invoked by alias); 15 Mar 2019 22:03:34 -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 82091 invoked by uid 89); 15 Mar 2019 22:03:33 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: =?ISO-8859-1?Q?Yes, score=8.1 required=5.0 tests=BAYES_99,BODY_8BITS,GARBLED_BODY,HTML_MESSAGE,INVALID_MSGID autolearn=no version=3.3.1 spammy=8:=bc, H*c:sk:boundar, HX-detected-operating-system:Windows, H*Ad:U*bug-gdb?= X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 15 Mar 2019 22:03:32 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:50495) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4uvK-0002FW-QK for gdb@sourceware.org; Fri, 15 Mar 2019 18:03:30 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:45428) by fencepost.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1h4uvK-0004q7-7A for bug-gdb@gnu.org; Fri, 15 Mar 2019 18:03:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h4uvJ-0002F4-KR for bug-gdb@gnu.org; Fri, 15 Mar 2019 18:03:30 -0400 Received: from [36.27.30.82] (port=62451 helo=fkfs.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4uvI-00028F-V5 for bug-gdb@gnu.org; Fri, 15 Mar 2019 18:03:29 -0400 Received: from desktop ([127.0.0.1]) by localhost via TCP with ESMTPA; Sat, 16 Mar 2019 05:57:37 +0800 Message-ID: 08eb4ed3-95b0-4cbd-a705-423aab54eee4 MIME-Version: 1.0 Sender: =?utf-8?Q?=E7=9E=A9=E7=9D=AC=E9=B9=8F?= From: =?utf-8?Q?=E7=9E=A9=E7=9D=AC=E9=B9=8F?= To: bug-gdb@gnu.org Date: Fri, 15 Mar 2019 22:03:00 -0000 Subject: =?utf-8?B?WW7lubVZeVpt55yfQU9556Wob3hSVlk=?= X-detected-operating-system: by eggs.gnu.org: Windows 7 or 8 X-Received-From: 36.27.30.82 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-SW-Source: 2019-03/txt/msg00034.txt.bz2 YnVnLWdkYkBnbnUub3Jn77yaDQpCd3dweOeUteOAgeW+riAxIDMgNyA9MiA0 IDMgMj0gMCAwIDcgNyDliJhOb2ENClJPY2dLSGYNCjA15pe2NTfliIYzN+en kg== >From gdb-return-46912-listarch-gdb=sources.redhat.com@sourceware.org Sat Mar 16 01:00:39 2019 Return-Path: Delivered-To: listarch-gdb@sources.redhat.com Received: (qmail 76423 invoked by alias); 16 Mar 2019 01:00:37 -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 76155 invoked by uid 89); 16 Mar 2019 01:00:22 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,UNSUBSCRIBE_BODY autolearn=no version=3.3.1 spammy=H*r:sk:gdb@sou, straight, discovering, HX-Received:a702 X-HELO: mail-pf1-f169.google.com Received: from mail-pf1-f169.google.com (HELO mail-pf1-f169.google.com) (209.85.210.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 16 Mar 2019 01:00:04 +0000 Received: by mail-pf1-f169.google.com with SMTP id v21so7442565pfm.12 for ; Fri, 15 Mar 2019 18:00:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=l29hWYourgbuX7lb+kN9nW4ZbJOFKcihyt2M0SCsAm8=; b=Cr58tyCemHX2SDJAtuX/SaYLklKbGhq63Vg3+WGrshX2acdiKKbytMxFcN27Ha8TDV Ep3ZagC5v/CYVEPxCiGUsxvvo1xQYtqVd8cdmx0QWMHO313vfMZRw9fuOwSnElwbW3rV Q4YXcrlCq51wqpB2xD5qtVcgWWO8bByEaNtRg3nlpPsbOcq3AXN5sRiylRiGpMz2n3Tq fIOr93Qa9MjhKVkzv3rL8DOu3k6QJDyzdjGfPdA72t7XEFagRl53+lMOXQyA8s74rRWj xqgiuMcToEKvNDIiZZDsKbYW7in13GGJQBMMLuY6SeQ/CqrLvZFBUS4c7vx1cQeZr5Wp QygQ== MIME-Version: 1.0 From: Artium Nihamkin Date: Sat, 16 Mar 2019 01:00:00 -0000 Message-ID: Subject: Need advice on writing gdb server for multiprocessor enviroment To: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-03/txt/msg00035.txt.bz2 Content-length: 950 Hi, We have a multiprocessor embedded system with built in hardware debugger that interface through a GPIB (IEEE-488) connection. A custom application acts as a debugger fronted and sends these GPIB commands. We were thinking of replacing this application with a gdb server with the eventual goal of debugging straight from a common, modern IDE. Using a gdb server seems like versatile and relatively easy to implement. The problem is that it is not clear how gdb, and specifically RSP, works with multiprocessor systems. Should we model each processor as a thread? The custom application has special commands such halting all processors at once, discovering which processors are present, getting the status of each processor (running/failed), XIO commands etc. Additionally there are several memory types with overlapping address spaces that the debugger can read/write to. Can all these things work reasonably with gdb? Thank you, Artium