jed-users mailing list

[2005 Date Index] [2005 Thread Index] [Other years]
[Thread Prev] [Thread Next]      [Date Prev] [Date Next]

Re: debug: points where left on the stack


"John E. Davis" <davis@xxxxxxxxxxxxx> wrote:
> Joerg Sommer <joerg@xxxxxxxxxxxx> wrote:
>>how can I identify functions where a value is left on the stack? Can
>>SLang add the line and the filename to every value where it came on the
>>stack and extract this information later?
>
> If you are using slang2, you might try using stkcheck.  To use it, put
>
>   require ("stkcheck");
>   enable_stack_check ();

This is not very useful, because it prints a message for every value left
on the stack. I'm using the stack often, which makes the output of
stkckeck unreadable.

I'm interested in functions they leave values on the stack after quit
without using the return statement. I'm not interested in such constructs:

do_check();
do_something();
if ( () )
...

or 

() = getbuf_info();
setbuf_info( (), old_buf_flags );

Do you have a tool for this?

Bye, Jörg.
-- 
Hügelschäfer's Law (http://www.bruhaha.de/laws.html):
Beiträge werden dort gepostet, wo sie den größten Widerstand hervorrufen.

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.


[2005 date index] [2005 thread index]
[Thread Prev] [Thread Next]      [Date Prev] [Date Next]