Adding backtrace calls to bochs debuggers as in gdb

Parfait Tokponnon <[email protected]> Sun, 25 Oct 2015 20:09:02 +0100
Newsgroups gmane.comp.emulators.bochs.devel
Message-ID <CAOfT3nHrRRHg35Jh3XK=i+qcC1JORgD4_J_Ccs4uuzdib6qzfA@mail.gmail.com>
Hello,
I want to suggest to Bochs developers community to add the backtrace
functionality to bochs debugger like in gdb. If you can make it also for
the GUI interface, it would be nice too.
I'm debugging a program with bochs debugger and I would very much like
navigate through the calls stack (backtrace) such as those functionalities
found in gdb (or ddd) which let you see the calls trace, so that you can
see the previous functions called before your program hit, for example, a
breakpoint.
I don't want to use gdb remote stubs.
I need it because now, I am experiencing an odd situation in the kernel i
am programming. It seems that it is looping endlessly and abnormally; and I
can't figure out why it is acting like that. The Log doesn't say anything
wrong and my print trace is also quite normal. So I think a backtrace would
be very nice to help me see which function is behaving wrongly.
But I think this tools would help other developers who may be in the same
situation. That is why I decide to write you.
Thank you for all your time taken to read my long mail.
Best regards,

-- 
Parfait T.

------------------------------------------------------------------------------

_______________________________________________
bochs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bochs-developers