From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Ada Community and GDB/Python problems
Date: Sat, 8 Feb 2020 11:27:04 +0100
Date: 2020-02-08T11:27:04+01:00 [thread overview]
Message-ID: <r1m2dn$d2o$1@gioia.aioe.org> (raw)
In-Reply-To: 4cc63bc8-ff8a-4f9e-8649-4e50d7448674@googlegroups.com
On 2020-02-07 23:39, joakimds@kth.se wrote:
> I would recommend tracing to "debug" what your application is doing (either print messages to standard out or logging to a file). In a multi-task application I've preferred tracing for a long time over stepping through code using a debugger like gdb.
I agree about tracing, but tracing too could be provided by the
debugger, without necessity to alter the source code.
Assuming the debugger is not the miserable mess GDB is.
> When using the GNAT Pro version of GNAT I've never had any issue with gdb and it has worked very well to step through code using it. However, rarely I've managed to get it working with the community edition and in my mind I've just thought about it like "if I want to use the debugger dbg I should use GNAT Pro". Maybe others in the Ada community has had a more positive experience with gdb using GNAT CE?
I never managed GDB working even in GNAT PRO.
--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de
prev parent reply other threads:[~2020-02-08 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 19:49 Ada Community and GDB/Python problems Rick Newbie
2020-02-07 22:39 ` joakimds
2020-02-08 6:19 ` J-P. Rosen
2020-02-09 17:28 ` Rick Newbie
2020-02-08 10:27 ` Dmitry A. Kazakov [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox