From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21093 invoked by alias); 17 Oct 2014 16:45:24 -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 21003 invoked by uid 89); 17 Oct 2014 16:45:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-yh0-f54.google.com Received: from mail-yh0-f54.google.com (HELO mail-yh0-f54.google.com) (209.85.213.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 17 Oct 2014 16:45:22 +0000 Received: by mail-yh0-f54.google.com with SMTP id z6so532085yhz.27 for ; Fri, 17 Oct 2014 09:45:20 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.29.172 with SMTP id i32mr3812171yha.179.1413564320158; Fri, 17 Oct 2014 09:45:20 -0700 (PDT) Received: by 10.170.140.214 with HTTP; Fri, 17 Oct 2014 09:45:20 -0700 (PDT) In-Reply-To: References: <543FBDFF.3050709@redhat.com> <104DEFBD-D686-4290-8E3C-725A51C165E6@dell.com> <7BB30632-15BE-4EF8-B84F-D35A27772F18@dell.com> Date: Fri, 17 Oct 2014 16:45:00 -0000 Message-ID: Subject: Re: recursion limit exceeded in Python API, but there's only one function in traceback From: Doug Evans To: =?UTF-8?Q?=C3=96mer_Sinan_A=C4=9Facan?= Cc: paul_koning , pmuldoon , gdb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2014-10/txt/msg00076.txt.bz2 On Thu, Oct 16, 2014 at 8:18 AM, =C3=96mer Sinan A=C4=9Facan wrote: > 2014-10-16 18:03 GMT+03:00 : >> Is that the handler for a breakpoint? Does the completion of the =E2=80= =9Csi=E2=80=9D command invoke the breakpoint handler? If yes, that=E2=80= =99s your answer. > > I see what you mean now. I think you're right... Yikes. If there is another breakpoint at the next instruction then ok, otherwise that feels unfortunate. [implementation detail bubbling up into the API, bleah]