Linked by Thom Holwerda on Thu 2nd May 2013 10:15 UTC
BeOS & Derivatives "In the past few weeks, I've managed to find a bit more free time to work on Haiku. As per usual, the lion's share of this time was spent on improving our integrated debugger. As such, I thought I'd give a brief overview of what's been added, and how it can be useful."
Thread beginning with comment 560326
To read all comments associated with this story, please click here.
Return values
by biffuz on Thu 2nd May 2013 11:55 UTC
biffuz
Member since:
2006-03-27

Showing return values of called functions is just awesome. Recently I've been using Netbeans and Eclipse (to work on Java, Android and PHP) and neither of them can do that (or perhaps I didn't figure it out yet - I didn't think it was possible, actually).
I have to try this thing out as soon as possible. Sadly, it's been years since I have done some serious work in C++, my favourite language (call me mad).

Reply Score: 3

RE: Return values
by ggeldenhuys on Thu 2nd May 2013 21:38 in reply to "Return values"
ggeldenhuys Member since:
2006-11-13

Delphi's integrated debugger has been doing that for years, and yes it is an awesome feature. I moved to Free Pascal development in recent years, where they use GDB as the debugger. Unfortunately GDB (with the Object Pascal language at least) can't do that either, and it is very frustrating.

Reply Parent Score: 2

RE[2]: Return values
by tylerdurden on Fri 3rd May 2013 06:44 in reply to "RE: Return values"
tylerdurden Member since:
2009-03-17

One of the shortcomings (or features, depending on the perspective) of GDB is that it expects some knowledge of the underlying architecture. On x86, for example, you just need to inspect the content of the EAX register for that context, which should hold the function's return value (in most cases.)

Reply Parent Score: 3