headers
Steve Donovan | 1 Jun 16:23
Picon

Re: Using GDB with SciTE

I forgot the obligatory screenshot ;)

http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/screenshot.png 

It shows execution pausing at a breakpoint, with a tooltip
evaluating the variable s. scite-gdb has some simplification
rules which make nasty types like std::string easier
to inspect

steve d.

--

-- 
This message is subject to the CSIR's copyright, terms and conditions and
e-mail legal notice. Views expressed herein do not necessarily represent the
views of the CSIR.

CSIR E-mail Legal Notice
http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html 

CSIR Copyright, Terms and Conditions
http://mail.csir.co.za/CSIR_Copyright.html 

For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR
Legal Notice send a blank message with REQUEST LEGAL in the subject line to
CallCentre <at> csir.co.za.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.
Permalink | Reply | 4 comments |
headers
Roy Wood | 1 Jun 16:48
Picon

Re: Using GDB with SciTE

> It shows execution pausing at a breakpoint, with a tooltip
> evaluating the variable s. scite-gdb has some simplification
> rules which make nasty types like std::string easier
> to inspect

This is seriously cool.

And you can do all this black magic just using the Lua module in Scite?
Permalink | Reply | 1 comment |
headers
Steve Donovan | 1 Jun 17:13
Picon

Re: Using GDB with SciTE

Well, Lua plus some C voodoo - but that was loaded dynamically
as a DLL and required no code changes to SciTE itself (except
for the tooltip)

It's a technique that has lots of other applications, like finally
providing configurable GUI widgets like file open boxes, etc.

steve d.

>>> "Roy Wood" <roy.wood <at> gmail.com> 01/06/2007 16:48 >>>
> It shows execution pausing at a breakpoint, with a tooltip
> evaluating the variable s. scite-gdb has some simplification
> rules which make nasty types like std::string easier
> to inspect

This is seriously cool.

And you can do all this black magic just using the Lua module in
Scite?
_______________________________________________
Scite-interest mailing list
Scite-interest <at> lyra.org 
http://mailman.lyra.org/mailman/listinfo/scite-interest

--

-- 
This message is subject to the CSIR's copyright, terms and conditions and
e-mail legal notice. Views expressed herein do not necessarily represent the
views of the CSIR.

CSIR E-mail Legal Notice
(Continue reading)

Permalink | Reply | 0 comments |
headers
J. Baltasar Garcia Perez-Schofield | 1 Jun 18:23
Picon

Re: Using GDB with SciTE


	Hi, there !

> I forgot the obligatory screenshot ;)
> http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/screenshot.png 
> 
> It shows execution pausing at a breakpoint, with a tooltip
> evaluating the variable s. scite-gdb has some simplification
> rules which make nasty types like std::string easier
> to inspect

	This is fantastic ! Will we see this improvement in next release ? When
is it planned to be ?

	Salud !

		Baltasar

--

PBC -- J. Baltasar García Perez-Schofield
jbgarcia en uvigo de es  http://webs.uvigo.es/jbgarcia/
Dep. Informática, Universidad de Vigo, España (Spain)
Permalink | Reply | 0 comments |
headers
Philippe Lhoste | 1 Jun 19:00
Picon

Re: Using GDB with SciTE

Interesting, I wonder if it is possible to do the same with DBGP 
<http://xdebug.org/docs-dbgp.php>, perhaps with LuaSocket.

--

-- 
Philippe Lhoste
--  (near) Paris -- France
--  http://Phi.Lho.free.fr
--  --  --  --  --  --  --  --  --  --  --  --  --  --
Permalink | Reply | 0 comments |
headers
noel frankinet | 1 Jun 16:40
Picon

Re: Using GDB with SciTE

Steve Donovan a écrit :
> Hi guys,
>
> I've recently been working on a Lua extension which allows
> you to debug using gdb in your favourite code editor. It
> currently only works with extman, but it would not be 
> difficult to extract the bits.  It uses the ability of SciTE
> Lua to dynamically load shared libraries; the spawner
> library uses the Director interface to pass spawned gdb
> output back to the Lua subsystem.
>
> No changes are required to the Win32 build; the GTK
> build requires loadlib to be enabled; instructions are
> provided.
>
> http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/scite-gdb.zip
>
> For the seriously impatient, there is a packed Sc1 build for 
> Windows:
>
> http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/sc1d.zip 
>
> And there's a modified tarball that can be built which will not
> interfere with your current SciTE installation; just unpack and
> go ./build (or build.bat); the GTK build will generate a 
> suitable shortcut (just run ./scited) which removes the
> existing director pipe, (due to an annoying 'feature' of
> the director interface, which only works if SciTE is
> allowed to recreate the pipe).
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
James Cuénod | 2 Jun 08:13
Picon

Re: Using GDB with SciTE

I would be interested to debug java from SciTE. Is this possible with any editor? Would it be possible with SciTE?

On 6/1/07, noel frankinet < noel.frankinet <at> skynet.be> wrote:
Steve Donovan a écrit :
> Hi guys,
>
> I've recently been working on a Lua extension which allows
> you to debug using gdb in your favourite code editor. It
> currently only works with extman, but it would not be
> difficult to extract the bits.  It uses the ability of SciTE
> Lua to dynamically load shared libraries; the spawner
> library uses the Director interface to pass spawned gdb
> output back to the Lua subsystem.
>
> No changes are required to the Win32 build; the GTK
> build requires loadlib to be enabled; instructions are
> provided.
>
> http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/scite-gdb.zip
>
> For the seriously impatient, there is a packed Sc1 build for
> Windows:
>
> http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/sc1d.zip
>
> And there's a modified tarball that can be built which will not
> interfere with your current SciTE installation; just unpack and
> go ./build (or build.bat); the GTK build will generate a
> suitable shortcut (just run ./scited) which removes the
> existing director pipe, (due to an annoying 'feature' of
> the director interface, which only works if SciTE is
> allowed to recreate the pipe).
>
> http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/scite173d.zip
>
> This modified version (apart from the loadlib fix) also enables
> Scintilla's tooltips which gdb.lua uses to show symbol values.
> Here are all the modified files:
>
> http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/changes173d.zip
>
> I'm interested in generalizing this to work with
> other debuggers, (particularly the Mono debugger and
> Python) if there's any interest.
>
> steve d.
>
>
>
>
I would be very interested to debug lua code from scite, would it be
possible ?

Regards
Noël Frankinet
_______________________________________________
Scite-interest mailing list
Scite-interest <at> lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest



--
Now go, and may the [open] source be with you 
_______________________________________________
Scite-interest mailing list
Scite-interest <at> lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest
Permalink | Reply | 0 comments |
headers
Steve Donovan | 2 Jun 10:35
Picon

Re: Using GDB with SciTE

I was thinking about debugging Java; there is a command-line debugger in the SDK which works rather like
GDB, so it's just a question of recognizing different patterns!

Although it would be better to generalize the existing code, so that support for extra debuggers could be
added as extensions: this is definitely the next thing I'll be doing.

steve d.

>>> "James Cuénod" <j3frea <at> gmail.com> 06/02/07 08:13 AM >>>
I would be interested to debug java from SciTE. Is this possible with any
editor? Would it be possible with SciTE?

On 6/1/07, noel frankinet <noel.frankinet <at> skynet.be> wrote:
>
> Steve Donovan a écrit :
> > Hi guys,
> >
> > I've recently been working on a Lua extension which allows
> > you to debug using gdb in your favourite code editor. It
> > currently only works with extman, but it would not be
> > difficult to extract the bits.  It uses the ability of SciTE
> > Lua to dynamically load shared libraries; the spawner
> > library uses the Director interface to pass spawned gdb
> > output back to the Lua subsystem.
> >
> > No changes are required to the Win32 build; the GTK
> > build requires loadlib to be enabled; instructions are
> > provided.
> >
> > http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/scite-gdb.zip
> >
> > For the seriously impatient, there is a packed Sc1 build for
> > Windows:
> >
> > http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/sc1d.zip
> >
> > And there's a modified tarball that can be built which will not
> > interfere with your current SciTE installation; just unpack and
> > go ./build (or build.bat); the GTK build will generate a
> > suitable shortcut (just run ./scited) which removes the
> > existing director pipe, (due to an annoying 'feature' of
> > the director interface, which only works if SciTE is
> > allowed to recreate the pipe).
> >
> > http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/scite173d.zip
> >
> > This modified version (apart from the loadlib fix) also enables
> > Scintilla's tooltips which gdb.lua uses to show symbol values.
> > Here are all the modified files:
> >
> > http://mysite.mweb.co.za/residents/sdonovan/scite-gdb/changes173d.zip
> >
> > I'm interested in generalizing this to work with
> > other debuggers, (particularly the Mono debugger and
> > Python) if there's any interest.
> >
> > steve d.
> >
> >
> >
> >
> I would be very interested to debug lua code from scite, would it be
> possible ?
>
> Regards
> Noël Frankinet
> _______________________________________________
> Scite-interest mailing list
> Scite-interest <at> lyra.org
> http://mailman.lyra.org/mailman/listinfo/scite-interest
>

-- 
Now go, and may the [open] source be with you

--

-- 
This message is subject to the CSIR's copyright, terms and conditions and
e-mail legal notice. Views expressed herein do not necessarily represent the
views of the CSIR.

CSIR E-mail Legal Notice
http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html 

CSIR Copyright, Terms and Conditions
http://mail.csir.co.za/CSIR_Copyright.html 

For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR
Legal Notice send a blank message with REQUEST LEGAL in the subject line to
CallCentre <at> csir.co.za.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.
Permalink | Reply | 0 comments |
headers
Neil Hodgson | 2 Jun 11:04
Picon

Re: Using GDB with SciTE

Steve Donovan:

> This modified version (apart from the loadlib fix) also enables
> Scintilla's tooltips which gdb.lua uses to show symbol values.

   This modification adds an OnDwellStart method to the Extension
interface which is a good feature. Since this interface is implemented
by downstream projects, they will not compile unless updated. To
minimize downstream breakage, a bundle of changes to Extension should
be made at one time. As well as OnDwellStart, Mitchell added OnKey.
Are there other good candidates? Adding parameters to existing
functions could be considered if there was a very good case.

   Neil
Permalink | Reply | 12 comments |
headers
Chachereau Nicolas | 2 Jun 14:25
Picon

Re: Re: Using GDB with SciTE

Neil Hodgson wrote:
>As well as OnDwellStart, Mitchell added OnKey.
>Are there other good candidates? Adding parameters to existing
>functions could be considered if there was a very good case.

One thing I'd like to see is an OnChange event. I think I saw something
similar mentioned in the interface, but afaik it is not implemented for Lua.

A use case would be a script for HTML editing that updates the closing tag
whevener the starting tag changes. I wrote this in Lua, and try to detect changes
with the OnChar event. It works quite well, but it isn't perfect. For example,
you might mistype something, say you want to change a <p> into a <div>, and you
type 'divb' while overwriting the 'p'. My script will update the closing tag to
be </divb>. You then press backspace to delete the 'b', but my script can't detect
it and can't update the closing tag. (The workaround is to do backspace twice
and type the 'v' again).

As this is probably very complicated (there are really many changes you
can make to a document, which means you have to think very carefully about how
to give enough information when calling OnChange() without making it too
bloated or hard to use) and I'm not capable of doing this myself, I guess
you might want to go on with the changes. Just wanted to mention it since you
were asking about changes to the extension interface.

Nicolas
Permalink | Reply | 5 comments |

Gmane