From: Petter <petter_fryklund@hotmail.com>
Subject: Re: DebugBreak() in Ada
Date: Tue, 25 Apr 2023 08:21:22 -0700 (PDT) [thread overview]
Message-ID: <ea6088fb-6e1e-4d8b-9286-072a5944b38en@googlegroups.com> (raw)
In-Reply-To: <kapuceFoq8mU1@mid.individual.net>
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
next prev parent reply other threads:[~2023-04-25 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 11:18 DebugBreak() in Ada Petter
2023-04-25 12:11 ` Niklas Holsti
2023-04-25 15:21 ` Petter [this message]
2023-04-25 17:22 ` Simon Wright
2023-04-25 17:20 ` Simon Wright
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox