From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
	ip-172-31-65-14.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_05,FREEMAIL_FROM,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Received: by 2002:a05:620a:129a:b0:74d:fdca:a6c6 with SMTP id w26-20020a05620a129a00b0074dfdcaa6c6mr2939795qki.14.1682436082946;
        Tue, 25 Apr 2023 08:21:22 -0700 (PDT)
X-Received: by 2002:a25:da89:0:b0:b99:efd5:2e05 with SMTP id
 n131-20020a25da89000000b00b99efd52e05mr1651081ybf.8.1682436082525; Tue, 25
 Apr 2023 08:21:22 -0700 (PDT)
Path: eternal-september.org!news.eternal-september.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 25 Apr 2023 08:21:22 -0700 (PDT)
In-Reply-To: <kapuceFoq8mU1@mid.individual.net>
Injection-Info: google-groups.googlegroups.com; posting-host=80.65.63.100; posting-account=ACEctQoAAAD3d42JSpp6_fpg88BhdFDo
NNTP-Posting-Host: 80.65.63.100
References: <74eb5c78-2212-48d8-beae-40b2b3ea6e69n@googlegroups.com> <kapuceFoq8mU1@mid.individual.net>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ea6088fb-6e1e-4d8b-9286-072a5944b38en@googlegroups.com>
Subject: Re: DebugBreak() in Ada
From: Petter <petter_fryklund@hotmail.com>
Injection-Date: Tue, 25 Apr 2023 15:21:22 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 2333
Xref: news.eternal-september.org comp.lang.ada:65139
List-Id: <comp.lang.ada>

tisdag 25 april 2023 kl. 14:12:02 UTC+2 skrev Niklas Holsti:
> On 2023-04-25 14:18, Petter wrote: 
> > I used some way to cause a DebugBreak() (programmatically causeng a 
> > break command in gdb) some 10 years ago. Now I can't find it. Perhaps 
> > one could raise int3? But I can't find how to either. Regards, 
> > Petter
> What do you mean by "causing a break command in gdb"? Do you intend to 
> run the program under gdb, and want to be able to insert something -- 
> perhaps a call DebugBreak -- in the Ada source to always cause a break 
> into gdb control at the point of that call, without having to set gdb 
> breakpoints at every call? 
> 
> It is not a fully automatic method, but you could write a null Ada 
> procedure DebugBreak and set a breakpoint in that procedure, manually 
> from gdb, before starting the program. Then every call to DebugBreak 
> will break, and you can look one level down in the call chain to see the 
> state at the point of call.

Sorry, I thougth DebugBreak() was familiar. If you in other languages not used by me call DebugBreak() i cuases the debugger to stop a running execution. I'm thought we had a similar for Ada. But I can be mistaken