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=-1.9 required=3.0 tests=BAYES_00,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: DebugBreak() in Ada Date: Tue, 25 Apr 2023 18:22:35 +0100 Organization: A noiseless patient Spider Message-ID: References: <74eb5c78-2212-48d8-beae-40b2b3ea6e69n@googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Info: dont-email.me; posting-host="1143267c6d309f8a5ee546d2f09da72a"; logging-data="1018990"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX192ADlYOOx55D9Cpq5j+XFtyJifeCRK1Mo=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (darwin) Cancel-Lock: sha1:n4kPKOAMwOzICLzDjqaf1n/aBxI= sha1:p70L7JBi1t3JvWDi1gXWn1XqIJs= Xref: news.eternal-september.org comp.lang.ada:65141 List-Id: Niklas Holsti writes: > 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. Great idea!