SciTE-debug 0.9.1 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News SciTE-debug 0.9.1 (Default branch)
# 1  
Old 04-10-2008
SciTE-debug 0.9.1 (Default branch)

Scite-debug is an extension for the popular SciTEeditor which allows several debugger backends tobe used. Breakpoints can be set visually andvalues evaluated by tooltip, etc. Currently, C/C++(gdb), Lua, and Python are fully supported. Thereis experimental support for Java and Mono.License: FreewareChanges:
When running GDB, scite-debug will now try todereference any pointer values automaticallywherever possible. It is now possible to debugshared libraries where the host program has nodebug symbols. As a special but important case,integrated Lua/C debugging is supported; it is nowpossible to step from Lua into C code.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. OS X (Apple)

Debug help

Hello, I was looking at kernel log's and found some parts what was "interesting" I previously started looking what has been going on in my computer because I had hacker attacks on my machine. Installed Avira & Little Snitch - softwares Previously my computer opened few folders what I have... (1 Reply)
Discussion started by: Scourge-
1 Replies

2. Programming

Debug Threads

How can we debug threaded application in Linux? If we have some doubt on a thread then how to set the context of that thread and how to check the values of variables for that thread? (1 Reply)
Discussion started by: rupeshkp728
1 Replies

3. Shell Programming and Scripting

If - then -else debug please

Can you help please ? ./get_df.sh: syntax error at line 13 : `then' unexpected #!/bin/ksh while : do PER=`df -h /DATA/ | nawk '{if (NR != 1) { sub (/%/,""); print $(NF-1)}}'` if then if] then mailx -s "FS over 90 per" me@company.com touch... (2 Replies)
Discussion started by: drbiloukos
2 Replies

4. OS X (Apple)

How to debug signals

Hi, In our program, we are using SIGTERM and i tired to put break point in this function. But my debuger is unable to brake at that point. I am working on Mac X and using XCode. Thanks (0 Replies)
Discussion started by: Saurabh78
0 Replies

5. Programming

debug with eclipse

Hi, i' m using eclipse 3.2.2 on ubuntu. When i debug a program (C language) i cannot see any variable in the variables view. From the console (debug perspective) i can see the message: no source file named class.c. What is the problem??? thanks (1 Reply)
Discussion started by: littleboyblu
1 Replies

6. AIX

debug aix 4.3

what's the best way for debugging in aix 4.3? i have this old aix 4.3 with unknown application that my new company still uses. they want me to complete a script that was working before but the application was very old and software company don't exist anymore. the script monitor the maintenance... (2 Replies)
Discussion started by: itik
2 Replies

7. Programming

how to debug

i am new to solaris i have one module which contain certain header files and sub modules i want ot execute the module and c what the values are beeing assigned to variables is makefile only solution for this is there any editor to help it,so that i can c the flow of the program and also... (1 Reply)
Discussion started by: ramneek
1 Replies

8. Programming

How to debug a C program?

Hi, I need to fix a C program someone wrote 10 years ago and I have very limited knowledge on C. Does someone know how to debug a C program? I am so used to VB debuger. The C program is on Unix SunOs Thanks for your help! (1 Reply)
Discussion started by: whatisthis
1 Replies
Login or Register to Ask a Question
DL(3)							     Library Functions Manual							     DL(3)

NAME
DL - generate logging messages in C and C++ using a debugger SYNOPSIS
#include <DL.h> DL(format,...) DLG(guard,format,...) DLH(handler,format,...) DLP(param,format,...) DLGH(guard,handler,format,...) DLHP(handler,param,format,...) DLGHP(guard,handler,param,format,...) DESCRIPTION
The DL macro is used to print logging or debugging messages using a debugger. The nana(1) command generates a set of debugger commands which are then sourced into gdb(1) to implement the logging. If you don't run the executable under gdb(1) then no tracing will occur. The arguments are: format,... - a printf(3) style argument list containing the message guard - print only if the guard is true. handler - the code that does the printing. Default: fprintf param - a parameter to be passed off to the handler. Default: stdout See nana.info for details on configuring the behaviour. SEE ALSO
nana-clg(1), nana(1), nana(3), I(3), DI(3), L(3), DL(3), Q(3) and nana.info. The nana.info file is the primary documentation for this library. AUTHOR
Phil Maker <pjm@gnu.org> DL(3)