Re: Save database?
- From: Dodji Seketeli <dodji seketeli org>
- To: Raymond Rogers <raymond rogers72 gmail com>
- Cc: nemiver-list gnome org
- Subject: Re: Save database?
- Date: Tue, 06 Jan 2015 23:38:11 +0100
Hello,
Sorry for my late reply to your email. It got into the moderation queue
of the mailing-list management system because you didn't subscribe to
the mailing list prior to posting, and then I totally overlooked the
notifications I got from the mailing-list management system. My bad.
Please find below my replies to your note.
Raymond Rogers <raymond rogers72 gmail com> a écrit:
I am just starting to try out nemiver so forgive me if this
information is somewhere in the manuals.
No problem.
I'm trying to debug some complicated math routines and need to
generate "trails" through various routines that can be checked and
compared by myself; a human.
Do you mean that you need to generate logs whenever control reaches
certain points of the program you are debugging?
If that is what you want, then I am thinking that maybe you should use
SystemTap[1] for that. It should allow you to write fairly sophisticated
scripts that let you monitor (and log) what happens during the execution
of the program you are interested in.
https://sourceware.org/systemtap/documentation.html
Since session saves are already included is there some way to
translate the database into a English information?
Hmmh. A Nemiver session is just a record of the context useful to debug
a program. That is, it contains things like the path to the program,
it's environment, the breakpoints you have set during the debugging and
things like that. It doesn't contain anything about the internals of
the program being debugged that you would need to be able to emit traces
about where you have stepped into. We could imagine adding a feature
like this in the future, though.
If not can somebody point me to somewhere in the code I could log the
instruction and data sequence.
Before I start pointing you to places int he code, I'd like to know if
you think that logging some context information each time the inferior
(the program being debugged) is stopped somewhere would be helpful to
you? By context information I mean things like "where you have
stopped". That can be file/line information of where you stopped at.
From that I guess you could get the source-code-level statements you
stopped at, etc. Would that be useful to your use case?
Cheers,
--
Dodji
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]