(ice-9 debug) is deprecated.

(ice-9 debug) is deprecated.

[Bruce Korb]

``(ice-9 debug) is deprecated. Use (system vm trace) for tracing.''

How far back into Guile history is "(system vm trace)" valid?
Viz. Is it there for 1.6.x?  If not, I have to continue using
it for a few more years.....

Re: (ice-9 debug) is deprecated.

[Ludovic Courtès]

Hi Bruce,

(system vm trace) appeared in Guile 2.0.

Thanks,
Ludo’.

Re: (ice-9 debug) is deprecated.

[Bruce Korb]

On 04/07/12 14:16, Ludovic Courtès wrote:
> Hi Bruce,
>
> (system vm trace) appeared in Guile 2.0.

Hi Ludovic,

Then I have a question:  Is this the currently accepted way of setting
up an environment where I can trace errors back to their source?

char fmt[] = "(use-modules (%s))\n"
             "(read-enable 'positions)\n"
             "(add-hook! before-error-hook error-source-line)\n"
             "(use-modules (ice-9 stack-catch))";
char post_2[] = "system vm trace";
char pre_2[] = "ice-9 debug";

asprintf(&p, fmt, (guile_ver >= 2) ? post_2 : pre_2);
ag_scm_eval_string_from_file_line(p, __FILE__, __LINE__);

Re: (ice-9 debug) is deprecated.

[Ludovic Courtès]

Hi Bruce,

Bruce Korb <bkorb@gnu.org> skribis:

> Then I have a question:  Is this the currently accepted way of setting
> up an environment where I can trace errors back to their source?

Currently uncaught errors lead to Guile printing a backtrace, normally.
Doesn’t it work for you?

Thanks,
Ludo’.

Re: (ice-9 debug) is deprecated.

[Bruce Korb]

Hi Ludovic,

On 04/09/12 10:29, Ludovic Courtès wrote:
>> Is this the currently accepted way of setting up an
>> environment where I can trace errors back to their source?
>
> Currently uncaught errors lead to Guile printing a backtrace, normally.
> Doesn’t it work for you?

The honest truth?  I found I had to go through this rigmarole to get
error info and file/line info way back when and haven't looked back.
If it is now the default to print out the problem at issue and the
file and line for where the problem was discovered, then I can
remove it.  I _would_ prefer to do that, but otherwise I need to do
what I can to get the file/line information.  So, can I eliminate
this stuff and still get what I need?

Thank you!!  Regards, Bruce

Re: (ice-9 debug) is deprecated.

[Andy Wingo]

On Mon 09 Apr 2012 13:00, Bruce Korb <bkorb@gnu.org> writes:

> Hi Ludovic,
>
> On 04/09/12 10:29, Ludovic Courtès wrote:
>>> Is this the currently accepted way of setting up an
>>> environment where I can trace errors back to their source?
>>
>> Currently uncaught errors lead to Guile printing a backtrace, normally.
>> Doesn’t it work for you?
>
> So, can I eliminate this stuff and still get what I need?

On Guile 2.0, I think so, as far as I know.  If you are still supporting
1.8, of course, you need #ifdeffery.

Andy
-- 
http://wingolog.org/

Re: (ice-9 debug) is deprecated.

[Bruce Korb]

On 04/09/12 13:44, Andy Wingo wrote:
>> So, can I eliminate this stuff and still get what I need?
>
> On Guile 2.0, I think so, as far as I know.  If you are still supporting
> 1.8, of course, you need #ifdeffery.

Thanks, Andy!
I still have to support 1.6.  1.8 is not going away any time soon.
Cheers - Bruce