On Jan 14 01:01, Neil Jerram wrote:
With Guile 1.8 or CVS, I find that the breakpoint doesn't even work
the first time! I'm still looking into that.
I use Guile from cvs tip too. And after you asked for Where did you
place the new breakpoint? I realized that the problem is with putting
the
Hi,
[Excuse me for the late reply. I was quite busy with setting up the
furnitures and just found chance to put my computer on a suitable
table.]
On Dec 29 02:29, Neil Jerram wrote:
Volkan YAZICI [EMAIL PROTECTED] writes:
While executing an s-exp with some breakpoints, everything goes
fine
Hi,
I think we should support emacs console users too. AFAIK, below lines
just work with emacs under X.
gds-scheme.el:
--
406 (define-key map [mouse-1] 'gds-show-last-stack)
407 (insert [click here to show error stack]
As an emacs user who prefers to use
Hi,
[I've some questions about guile-debugging package and because of I
couldn't find a suitable place to ask, I decided to post them in here.
I hope it's ok.]
While executing an s-exp with some breakpoints, everything goes
fine. But after I finish the execution and want to re-execute the code
On Oct 31 09:43, Neil Jerram wrote:
I'm not sure what you mean by a new scope in C code. C code must
always obey C's rules, of course.
Perhaps you mean that the C code has some Scheme code that it wants to
eval, but that it doesn't want it to make any lasting bindings.
Then I guess you
Hi,
On Oct 13 02:30, Ludovic Courtès wrote:
Looks like nobody answered you, so here we go.
Thanks so much for your detailed post. I solved (a small part of) my
problem by invoking scm_init_guile() just at the start of the backend
process. (But caching parse plans is still a PITA for now.) OTOH,
Hi,
I'm executing seperate procedures in the same Guile session initialized
by scm_init_guile(). Just after initialization, some global definitions
get loaded. While executing supplied procedures sequentially, I want to
restrict their access to some variables. Namely I want to set some
Hi,
I need such a feature:
/*
* If there's an already running guile process in the background,
* return it, otherwise create a new one and return new process.
*/
interp = guile_interp(...);
With such a functionality, it'd be possible to
- Parse execute faster. (We won't need to
On Aug 28 11:21, Neil Jerram wrote:
A common requirement is to be able to show as much useful context as
possible when a Scheme program hits an error. The most immediate
information about an error is the kind of error that it is - such as
division by zero - and any parameters that the code
On Jul 31 10:53, dave wrote:
I had to work through this a while back, and the problem I had was that
there are two types of error handler callback - one is called before the
stack is unwound, the other after. If you only set the error callback
for after the unwind there is no stack to do the
On Jul 29 03:08, Clinton Ebadi wrote:
You should be able to put something like:
SCM_DEVAL_P = 1;
SCM_RECORD_POSITIONS_P = 1;
SCM_BACKTRACE_P = 1;
SCM_RESET_DEBUG_MODE;
Into your real_main (the one passed to scm_boot_guile). This will give
you debug output similar
11 matches
Mail list logo
