Nabble - Komodo - General

is out of the office.

2008-11-20T11:55:12Z

I will be out of the office starting 13/11/2008 and will not return until
21/11/2008.

In case of urgency, please contact one of my colleagues:
* Anne Snijkers (anne.snijkers@...)
* Tanja VanDamme (tanja.vandamme@...)
* Christiaan Ziccardi (christiaan.ziccardi@...)
* Vincent De Backer (vincent.debacker@...).
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Komodo IDE and Edit 5.0.2 released

2008-11-20T11:50:30Z

Komodo 5.0.2 has now been released. You can use Komodo's auto-update
menu "Help->Check for Updates...", or you can download it directly from
here:

http://www.activestate.com/Products/komodo_ide/index.mhtml
http://www.activestate.com/Products/komodo_ide/komodo_edit.mhtml

This is mostly a bug fix release. You can check out the full details of
what has been fixed and changed in the release notes:

http://docs.activestate.com/komodo/5.0/releases/ide.html#bug_fixes-5.0.2

We welcome your feedback:

email: http://listserv.activestate.com/mailman/listinfo/komodo-discuss
bugs: http://bugs.activestate.com/enter_bug.cgi?product=Komodo
forums: http://community.activestate.com/products/Komodo

Cheers,
Todd

--
Todd Whiteman - "Komodo roper"

_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: [TDK] Tcl remote debugger and spawnpoints

2008-11-20T04:42:19Z

Thank you, Andreas, for getting to the bottom of this.

Hemang.
Andreas Kupries wrote:

> I finally managed to repro it here, overcoming a different bug in Komodo
> itself too.
>
> It is a bug in the spawn handling of dbgp_tcldebug ...
>
> * Using Tcl 8.5, and snit 2 the command resolution changed subtly.
>
> * This caused an [eval] in the spawn processing to not be the
> core ::eval, but an app internal command.
>
> * This is turn caused the port number for the new session to be
> some Tcl command string instead of a number, and appLaunch.tcl
> then threw an error on that, exiting silently.
>
> I will rebuild the dbgp_tcldebug(.exe).
>
> --
> Andreas Kupries <andreask@...>
> Developer @ http://www.ActiveState.com
> Tel: +1 778-786-1122
>
>
>
>> -----Original Message-----
>> From: tdk-bounces@...
>> [mailto:tdk-bounces@...]On Behalf Of Andreas
>> Kupries
>> Sent: Wednesday, November 19, 2008 12:19 PM
>> To: Hemang Lavana; Alex Panchenko
>> Cc: Jeff Hobbs; dbgp@...;
>> komodo-discuss@...; tdk@...
>> Subject: Re: [TDK] [Komodo-discuss] Tcl remote debugger and spawnpoints
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: tdk-bounces@...
>>> [mailto:tdk-bounces@...]On Behalf Of Hemang Lavana
>>> Sent: Tuesday, November 18, 2008 1:53 PM
>>> To: Alex Panchenko
>>> Cc: Jeff Hobbs; dbgp@...;
>>> komodo-discuss@...; tdk@...
>>> Subject: Re: [TDK] [Komodo-discuss] Tcl remote debugger and spawnpoints
>>>
>>>
>>> Hi all,
>>>
>>> Any updates on whether this issue has been resolved or not?
>>>
>>> Thanks,
>>> Hemang.
>>> Alex Panchenko wrote:
>>>
>>>> Hi,
>>>>
>>>> Here is the detailed information.
>>>>
>> Reading closely
>>
>>
>>>> There are to files: parent.tcl and child.tcl
>>>>
>>>> === parent.tcl ===
>>>> proc spawn {cmd args} {
>>>> puts [exec [info nameofexecutable] $cmd $args]
>>>> }
>>>>
>>>> puts "PARENT STARTED"
>>>> spawn child.tcl
>>>> puts "PARENT FINISHED"
>>>> === child.tcl ====
>>>> puts "CHILD STARTED"
>>>> puts "CHILD FINISHED"
>>>> ==================
>>>>
>> Looking ok.
>>
>>
>>>> The contents of the files is based on the
>>>> http://docs.activestate.com/tdk/5.0/Debugger.html#mult_processes
>>>>
>>>> The command line used to start debugger is (all on the same line):
>>>> C:\TCL-Debug\5\dbgp_tcldebug.exe
>>>> -dbgp 192.168.3.135:10000
>>>> -app-shell C:\Tcl85\bin\tclsh85.exe
>>>> -ide-key dbgp_1225872443074
>>>> -log -logfile C:\TCL-Debug\log
>>>> -app-file C:\home\tcl-spawnpoints\parent.tcl --
>>>>
>> Looks ok as well, knows where to find Komodo, or rather your frontend app.
>>
>>
>>>> DBGP request:
>>>> spawnpoint_set -s enabled -n 6 -i 68 -f
>>>> file:///C:/home/tcl-spawnpoints/parent.tcl
>>>>
>> Looks ok as well
>>
>>
>>>> DBGP response:
>>>> <?xml version="1.0" encoding="UTF-8" ?>
>>>> <response xmlns="urn:debugger_protocol" command="spawnpoint_set"
>>>> transaction_id="68" state="enabled" id="0" />
>>>>
>> And is accepted. So, dbgp_tcldebug, and the application under debug agree
>> that this is a spawnpoint.
>>
>>
>>
>>>> After that:
>>>> run -i 70
>>>>
>>>> response:
>>>> - a few stream/OUTPUT packets, followed by
>>>> <?xml version="1.0" encoding="UTF-8" ?>
>>>> <response xmlns="urn:debugger_protocol" command="run"
>>>> transaction_id="70" status="stopping" reason="ok" />
>>>>
>>>> Debuggger log:
>>>> The whole log file size is about 200kb, the spawnpoint
>>>>
>> handling part is:
>>
>>>> ...
>>>> LOG(timing,3271527680): HandleNubEvent ENTER
>>>> LOG(message,3271527680): reading 105 bytes
>>>> LOG(message,3271527680): got (105): 'SPAWN_RQ {{0 {} global} {0
>>>>
>>> {1 6 {97
>>>
>>>> 16}} source C:/home/tcl-spawnpoints/parent.tcl}} {} {spawn child.tcl}'
>>>> LOG(timing,3271527680): HandleNubEvent SPAWN_RQ
>>>> debug | appState = stopped (traced, sync'd)
>>>> LOG(timing,3271527680): DeliverEvent stdin ()
>>>> debug | appState = running (traced, sync'd)
>>>>
>> The application under debug recognizes the spawnpoint, has invoked the
>> internal replacement for 'spawn' and asks dbgp_tcldebug for the relevant
>> info (SPAWN_RQ).
>>
>>
>>
>>>> LOG(message,3271527680): sent: len=117 'SPAWN_ACK alex
>>>> {::dbgp::client::Spawn request {spawn child.tcl} ::client}
>>>>
>> The debugged application has received the spawn info from dbgp_tcldebug
>> (SPAWN_ACK)
>> Per the attached spawn.pdx is will run the child process, except
>> if no port
>> was specified (= denied). I do not see that.
>>
>>
>>
>>>> C:/TCL-Debug/5/appLaunch.tcl {} tcldbgp2472'
>>>> LOG(timing,3271542680): HandleNubEvent ENTER
>>>> ...
>>>>
>>>> Output:
>>>> PARENT STARTED
>>>> PARENT FINISHED
>>>>
>>>> Output if there is no spanwpoint or if spawnpoint is disabled:
>>>> PARENT STARTED
>>>> CHILD STARTED
>>>> CHILD FINISHED
>>>> PARENT FINISHED
>>>>
>>>> So it looks like the new process is not started if there is a
>>>>
>>> spawnpoint.
>>>
>> Which, according to the spawn.pdx code can happen only if there is a Tcl
>> error before the exec.
>>
>> The other possibility is that the child process is launched, but something
>> in its initialization fails before the user code is reached, and then it
>> silently exits. Like for example, does
>>
>> C:/TCL-Debug/5/appLaunch.tcl
>>
>> exist ? That is the actual entrypoint for the child, to initialize the
>> debugger nub in the child, before child.tcl is run.
>>
>> One thing which could be done would be to add 'puts' statements to the
>> appLaunch file which writes to a fixed log file on the box. After the
>> failing run check how much of that file is executed per these puts. If
>> something happens there before child.tcl is run ... Well, as said above,
>> that would be a very silent exit.
>>
>>
>>
>>
>>
>>>> Also, it should made subsequent DBGP connection from the
>>>>
>> child process,
>>
>>>> but it also does not happen.
>>>>
>> If something goes wrong with the child process startup the dbgp_tcldebug
>> will not open a connection, as it has no new session to open it for. I.e.
>> this is likely a follow-on behaviour to the original problem.
>>
>>
>>
>>>> It should be enough information to reproduce the issue. If you
>>>>
>>> need more
>>>
>>>> information - please let me know.
>>>>
>>>> Thanks,
>>>> Alex
>>>>
>>>>
>>>> Jeff Hobbs wrote:
>>>>
>>>>
>>>>> Alex Panchenko wrote:
>>>>>
>>>>>
>>>>>> I am not sure what mailing list should be used for my question, so I
>>>>>> will post to all related ones.
>>>>>>
>>>>>> I am interested in the DBGP support of the spawnpoints. Does tcl
>>>>>> remote debugger support spawnpoints?
>>>>>>
>>>>>> At the moment Komodo IDE does not allow me even to setup spawnpoints
>>>>>> when remote debugger is attached.
>>>>>> I can debug the same code with spawnpoint using Tcl Dev Kit
>>>>>>
>> Debugger,
>>
>>>>>> but it looks like it uses proprietary protocol to communicate with
>>>>>> the launched process.
>>>>>>
>>>>>>
>>>>> Yes, the TDK Debugger uses a different Tcl-oriented protocol as it
>>>>> preceded dbgp and was designed just for Tcl. The debugger backends
>>>>> between TDK and Komodo use the same debugging core for Tcl though.
>>>>> There handling of spawnpoints will vary as the protocol
>>>>>
>> allows, but as
>>
>>>>> it is the debugging core with the support, it should be "the same".
>>>>>
>>>>>
>>>>>
>>>>>> Back to the DBGP: I can send spawnpoint_set command (and verify the
>>>>>> result with spawnpoint_list), but when the process reaches the
>>>>>> specified line nothing happens. Should I use some undocumented
>>>>>> commands to make it work, is it a bug or a missing feature?
>>>>>>
>>>>>> My configuration is
>>>>>> - Windows XP
>>>>>> - Tcl 8.4
>>>>>> - latest tcl remote debugger
>>>>>>
>>>>>>
>>>>> In my testing, one obvious variation that I noted was that TDK will
>>>>> report invalid spawnpoint lines (lines not recognized by the debugger
>>>>> as allowable spawn points). In TDK, a dialog will show to indicate
>>>>> this, but I received no such feedback from Komodo.
>>>>>
>>>>> Currently only [exec], [spawn] and [thread::create] are recognized
>>>>> spawn point generators. This is a hardcoded core list (unless you
>>>>> extend with .pdx files), and I noticed one quirk about this ...
>>>>> exp_spawn was not recognized, whereas spawn was. This is
>>>>>
>> something we
>>
>>>>> need to correct.
>>>>>
>>>>> In any case, that may be what you hit. You are using the
>>>>>
>> correct dbgp
>>
>>>>> commands though. Can you describe in more detail the tests you are
>>>>> using? Have you tried running dbgp_tcldebug with -log (activate
>>>>> logging) and -logfile myfile.txt (redirect log from stdout to file)?
>>>>> That should provide more detailed information.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Jeff
>>>>>
>>>>>
>>>> _______________________________________________
>>>> TDK mailing list
>>>> TDK@...
>>>> http://listserv.ActiveState.com/mailman/listinfo/tdk
>>>>
>>>>
>>> _______________________________________________
>>> TDK mailing list
>>> TDK@...
>>> http://listserv.ActiveState.com/mailman/listinfo/tdk
>>>
>> --
>> Andreas Kupries <andreask@...>
>> Developer @ http://www.ActiveState.com
>> Tel: +1 778-786-1122
>>
>>
>>
>
> _______________________________________________
> TDK mailing list
> TDK@...
> http://listserv.ActiveState.com/mailman/listinfo/tdk
>

_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: [TDK] Tcl remote debugger and spawnpoints

2008-11-18T13:53:09Z

Hi all,

Any updates on whether this issue has been resolved or not?

Thanks,
Hemang.
Alex Panchenko wrote:

> Hi,
>
> Here is the detailed information.
>
> There are to files: parent.tcl and child.tcl
>
> === parent.tcl ===
> proc spawn {cmd args} {
> puts [exec [info nameofexecutable] $cmd $args]
> }
>
> puts "PARENT STARTED"
> spawn child.tcl
> puts "PARENT FINISHED"
> === child.tcl ====
> puts "CHILD STARTED"
> puts "CHILD FINISHED"
> ==================
>
> The contents of the files is based on the
> http://docs.activestate.com/tdk/5.0/Debugger.html#mult_processes
>
> The command line used to start debugger is (all on the same line):
> C:\TCL-Debug\5\dbgp_tcldebug.exe
> -dbgp 192.168.3.135:10000
> -app-shell C:\Tcl85\bin\tclsh85.exe
> -ide-key dbgp_1225872443074
> -log -logfile C:\TCL-Debug\log
> -app-file C:\home\tcl-spawnpoints\parent.tcl --
>
> DBGP request:
> spawnpoint_set -s enabled -n 6 -i 68 -f
> file:///C:/home/tcl-spawnpoints/parent.tcl
>
> DBGP response:
> <?xml version="1.0" encoding="UTF-8" ?>
> <response xmlns="urn:debugger_protocol" command="spawnpoint_set"
> transaction_id="68" state="enabled" id="0" />
>
> After that:
> run -i 70
>
> response:
> - a few stream/OUTPUT packets, followed by
> <?xml version="1.0" encoding="UTF-8" ?>
> <response xmlns="urn:debugger_protocol" command="run"
> transaction_id="70" status="stopping" reason="ok" />
>
> Debuggger log:
> The whole log file size is about 200kb, the spawnpoint handling part is:
>
> ...
> LOG(timing,3271527680): HandleNubEvent ENTER
> LOG(message,3271527680): reading 105 bytes
> LOG(message,3271527680): got (105): 'SPAWN_RQ {{0 {} global} {0 {1 6 {97
> 16}} source C:/home/tcl-spawnpoints/parent.tcl}} {} {spawn child.tcl}'
> LOG(timing,3271527680): HandleNubEvent SPAWN_RQ
> debug | appState = stopped (traced, sync'd)
> LOG(timing,3271527680): DeliverEvent stdin ()
> debug | appState = running (traced, sync'd)
> LOG(message,3271527680): sent: len=117 'SPAWN_ACK alex
> {::dbgp::client::Spawn request {spawn child.tcl} ::client}
> C:/TCL-Debug/5/appLaunch.tcl {} tcldbgp2472'
> LOG(timing,3271542680): HandleNubEvent ENTER
> ...
>
> Output:
> PARENT STARTED
> PARENT FINISHED
>
> Output if there is no spanwpoint or if spawnpoint is disabled:
> PARENT STARTED
> CHILD STARTED
> CHILD FINISHED
> PARENT FINISHED
>
> So it looks like the new process is not started if there is a spawnpoint.
>
> Also, it should made subsequent DBGP connection from the child process,
> but it also does not happen.
>
> It should be enough information to reproduce the issue. If you need more
> information - please let me know.
>
> Thanks,
> Alex
>
>
> Jeff Hobbs wrote:
>
>> Alex Panchenko wrote:
>>
>>> I am not sure what mailing list should be used for my question, so I
>>> will post to all related ones.
>>>
>>> I am interested in the DBGP support of the spawnpoints. Does tcl
>>> remote debugger support spawnpoints?
>>>
>>> At the moment Komodo IDE does not allow me even to setup spawnpoints
>>> when remote debugger is attached.
>>> I can debug the same code with spawnpoint using Tcl Dev Kit Debugger,
>>> but it looks like it uses proprietary protocol to communicate with
>>> the launched process.
>>>
>> Yes, the TDK Debugger uses a different Tcl-oriented protocol as it
>> preceded dbgp and was designed just for Tcl. The debugger backends
>> between TDK and Komodo use the same debugging core for Tcl though.
>> There handling of spawnpoints will vary as the protocol allows, but as
>> it is the debugging core with the support, it should be "the same".
>>
>>
>>> Back to the DBGP: I can send spawnpoint_set command (and verify the
>>> result with spawnpoint_list), but when the process reaches the
>>> specified line nothing happens. Should I use some undocumented
>>> commands to make it work, is it a bug or a missing feature?
>>>
>>> My configuration is
>>> - Windows XP
>>> - Tcl 8.4
>>> - latest tcl remote debugger
>>>
>> In my testing, one obvious variation that I noted was that TDK will
>> report invalid spawnpoint lines (lines not recognized by the debugger
>> as allowable spawn points). In TDK, a dialog will show to indicate
>> this, but I received no such feedback from Komodo.
>>
>> Currently only [exec], [spawn] and [thread::create] are recognized
>> spawn point generators. This is a hardcoded core list (unless you
>> extend with .pdx files), and I noticed one quirk about this ...
>> exp_spawn was not recognized, whereas spawn was. This is something we
>> need to correct.
>>
>> In any case, that may be what you hit. You are using the correct dbgp
>> commands though. Can you describe in more detail the tests you are
>> using? Have you tried running dbgp_tcldebug with -log (activate
>> logging) and -logfile myfile.txt (redirect log from stdout to file)?
>> That should provide more detailed information.
>>
>> Regards,
>>
>> Jeff
>>
> _______________________________________________
> TDK mailing list
> TDK@...
> http://listserv.ActiveState.com/mailman/listinfo/tdk
>

Re: [Komodo-beta] Linux crashes - crashreporter

2008-11-18T13:22:26Z

Anton Visser wrote:
> Todd, my Komodo seems to be crashing a lot, and the crash reports are
> still in the ~/.komodoide/5.0/host-<YOURHOST>/XRE/.activestate/komodo
> ide/Crash Reports/pending folder.
>
> Is there anyway for you to tell if you are getting my crash reports?

Hi Anton,

When submitting the crash report, the crash report dialog will either
display a notification of "submitted successfully", or "failed to
submit". If your getting the later (i.e. it failed), then the crash
report will be stored in the "Crash Reports/pending" folder.

If you include your email address in the submission report I could check
against the existing submitted crash reports, otherwise there is no way
to find out who the report came from, and just checking I do not see any
reports that have the email field containing "visseraj".

You can still send any unsuccessful crash report submissions to me, and
I can examine these reports manually, include as much relevant
information on what you were doing at the time of the crash.

Thanks,
Todd
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: [Komodo-beta] Linux crashes - crashreporter

2008-11-18T12:59:50Z

Todd, my Komodo seems to be crashing a lot, and the crash reports are
still in the ~/.komodoide/5.0/host-<YOURHOST>/XRE/.activestate/komodo
ide/Crash Reports/pending folder.

Is there anyway for you to tell if you are getting my crash reports?

cheers,
Anton

On Wed, Oct 22, 2008 at 1:13 PM, Todd Whiteman <toddw@...> wrote:

> Davide Ficano wrote:
>> Todd Whiteman ha scritto:
>>> Hi,
>>>
>>> For the Linux users out there, in the case of a crash, the Komodo
>>> crashreporter is likely failing when trying to send in the crash report
>>> to ActiveState [1] (if you have been able to successfully send in
>>> crashreports, I'd like to know).
>>>
>>> The the crash reports are still stored on your Linux computer, inside of
>>> your Komodo profile directory. The location is:
>>> $ ~/.komodoide/5.0/host-<YOURHOST>/XRE/.activestate/komodo ide/Crash
>>> Reports/pending
>>>
>>> We are still interested in receiving crash reports for Linux, so if you
>>> can manually archive this directory and send it to
>>> support@... (or to myself) then it would be appreciated and
>>> this will aid us to track down any Linux crashes.
>>>
>>> For those that want to examine the crashes themselves, you can will need
>>> to download, build and install google-breakpad [2]. Then you can use it as:
>>> $ breakpad/bin/minidump_stackwalk path_to_crash_report_file.dmp
>>>
>>
>> Hi Todd,
>>
>> thanks for these useful infos.
>> I've submitted a couple of crashes but I'm unable to view reports at
>>
>> https://crash-reports.komodo.activestate.com/submit/report/index/
>>
>> The server seems unreachable
>>
>> Due to the fact I've successfully submitted crash reports all .dmp file are removed
>> so I can't use breakpad to debug myself.
>
>
> Hi Davide,
>
> I don't believe the crash report website has been setup to display
> submitted crash reports.
>
> If you do have another crash and want to examine them using breakpad
> yourself, when the crash report dialog appears, the ".dmp" files will be
> accessible in the pending folder at that time, so you can run the
> stackdump utility then, or make a copy the files before submitting the
> report.
>
> Cheers,
> Todd
> _______________________________________________
> Komodo-beta mailing list
> Komodo-beta@...
> http://listserv.ActiveState.com/mailman/listinfo/komodo-beta
>

Re: saving state

2008-11-17T08:28:48Z

Thanks Eric for the macro piece, that works well, except for the
minimize on save all bug. I got around that by making the minized size
full screen.

Thanks Todd for the insight on where this is going.

cheers,
Anton

On Fri, Nov 14, 2008 at 12:28 PM, Todd Whiteman <toddw@...> wrote:

> Anton Visser wrote:
>>
>> I am running Ubuntu and just turned on compizfusion which is causing
>> problems with Komodo. I am going to turn it off, but it give me a
>> feature request. Is it possible to make Komodo save state as files
>> are opened/closed, or projects are opened/closed. It appears that you
>> have to close Komodo to save state, so that the next time it opens,
>> the files/projects you were working on, are open. After a crash, it
>> sucks to have to go and close files/projects that you closed, and open
>> the files that you were working on.
>
> Hi Anton,
>
> Note that we do wish to offer better state saving of the Komodo workspace,
> such as you have described, we have the following bug logged for this
> feature:
> http://bugs.activestate.com/show_bug.cgi?id=79489
>
> We nearly added it in 5.0.0 or 5.0.1, but decided against this until we can
> also provide an alternative way to start Komodo without restoring the
> workspace, in case something in the workspace is causing Komodo to fault.
>
> Cheers,
> Todd
>

Re: saving state

2008-11-14T10:28:24Z

Anton Visser wrote:
> I am running Ubuntu and just turned on compizfusion which is causing
> problems with Komodo. I am going to turn it off, but it give me a
> feature request. Is it possible to make Komodo save state as files
> are opened/closed, or projects are opened/closed. It appears that you
> have to close Komodo to save state, so that the next time it opens,
> the files/projects you were working on, are open. After a crash, it
> sucks to have to go and close files/projects that you closed, and open
> the files that you were working on.

Hi Anton,

Note that we do wish to offer better state saving of the Komodo
workspace, such as you have described, we have the following bug logged
for this feature:
http://bugs.activestate.com/show_bug.cgi?id=79489

We nearly added it in 5.0.0 or 5.0.1, but decided against this until we
can also provide an alternative way to start Komodo without restoring
the workspace, in case something in the workspace is causing Komodo to
fault.

Cheers,
Todd
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: saving state

2008-11-14T10:09:39Z

Hi, Anton,

Running [File|Save All] will save state.

You could also add trigger macros on

"After file open" and "After file close" (you need
a separate macro for each one), with this code:

ko.commands.doCommand('cmd_saveAll');

To track projects, add notification macros that watch
project_added and project_removed, with the same
line of code.

- Eric

Anton Visser wrote:

> I am running Ubuntu and just turned on compizfusion which is causing
> problems with Komodo. I am going to turn it off, but it give me a
> feature request. Is it possible to make Komodo save state as files
> are opened/closed, or projects are opened/closed. It appears that you
> have to close Komodo to save state, so that the next time it opens,
> the files/projects you were working on, are open. After a crash, it
> sucks to have to go and close files/projects that you closed, and open
> the files that you were working on.
>
> cheers,
> Anton
> _______________________________________________
> Komodo-discuss mailing list
> Komodo-discuss@...
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
> Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

saving state

2008-11-14T08:02:19Z

I am running Ubuntu and just turned on compizfusion which is causing
problems with Komodo. I am going to turn it off, but it give me a
feature request. Is it possible to make Komodo save state as files
are opened/closed, or projects are opened/closed. It appears that you
have to close Komodo to save state, so that the next time it opens,
the files/projects you were working on, are open. After a crash, it
sucks to have to go and close files/projects that you closed, and open
the files that you were working on.

cheers,
Anton
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: Changing the behavior of the "Section List" box

2008-11-10T16:47:10Z

Trent Mick wrote:

> Todd Whiteman wrote:
>> Trent Mick wrote:
>>> Mathieu Longtin wrote:
>>>> Does the code have to be in komodo.jar, or can it stay unzipped?
>>> Now edit "komodo.manifest" by replacing all instances of:
>>>
>>> jar:komodo.jar!
>>>
>>> with
>>>
>>> tmp
>>
>> Actually, you'll need to include the trailing "/" too, so replace:
>> "jar:komodo.jar!/"
>> with
>> "tmp"
>
>
> Before:
> content komodo jar:komodo.jar!/content/ xpcnativewrappers=yes
> After:
> content komodo tmp/content/ xpcnativewrappers=yes
>
> So I think the replacement is as I said it, no?

Yes, your right. Sorry for jump'n in :D
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: Changing the behavior of the "Section List" box

2008-11-10T16:15:13Z

Todd Whiteman wrote:

> Trent Mick wrote:
>> Mathieu Longtin wrote:
>>> Does the code have to be in komodo.jar, or can it stay unzipped?
>> Now edit "komodo.manifest" by replacing all instances of:
>>
>> jar:komodo.jar!
>>
>> with
>>
>> tmp
>
> Actually, you'll need to include the trailing "/" too, so replace:
> "jar:komodo.jar!/"
> with
> "tmp"

Before:
content komodo jar:komodo.jar!/content/ xpcnativewrappers=yes
After:
content komodo tmp/content/ xpcnativewrappers=yes

So I think the replacement is as I said it, no?

Trent

--
Trent Mick
trentm at activestate.com
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: Changing the behavior of the "Section List" box

2008-11-10T12:59:05Z

Trent Mick wrote:

> Mathieu Longtin wrote:
>> Does the code have to be in komodo.jar, or can it stay unzipped?
>
> Now edit "komodo.manifest" by replacing all instances of:
>
> jar:komodo.jar!
>
> with
>
> tmp

Actually, you'll need to include the trailing "/" too, so replace:
"jar:komodo.jar!/"
with
"tmp"

Cheers,
Todd

_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: Changing the behavior of the "Section List" box

2008-11-10T09:54:20Z

Mathieu Longtin wrote:
> Does the code have to be in komodo.jar, or can it stay unzipped?

It either has to be in komodo.jar or you have to change
"komodo.manifest" (it is beside the komodo.jar file) to tell Mozilla
that the "komodo" chrome is not in a .jar.

Here is what I do when I want to play like this. (WARNING: Things are
going to break with Komodo's auto-update system.)

# This dir is different on Mac OS X. I'm using Linux commands
# here, but the Windows equivalents should be obvious.
cd $installdir/lib/mozilla/chrome
mkdir tmp
cd tmp
unzip -q ../komodo.jar

Now edit "komodo.manifest" by replacing all instances of:

jar:komodo.jar!

with

tmp

Re-start Komodo and it should be using the unzipped version of Komodo
chrome. You can make a trivial change to some visible string attribute
(e.g., go edit the "title" attribute on <window> in the "about.xul"
About dialog).

Trent

--
Trent Mick
trentm at activestate.com
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: Changing the behavior of the "Section List" box

2008-11-10T07:12:35Z

Does the code have to be in komodo.jar, or can it stay unzipped?

--
Mathieu Longtin
1-514-803-8977

On Fri, Nov 7, 2008 at 6:21 PM, Trent Mick <trentm@...> wrote:

Mathieu Longtin wrote:

Here, sorry, this is not a real patch diff, I just overwrote the original.
I'm leaving the priority as is, it's doubtful any symbol will be a number, since most languages require identifier to start with a letter or underscore.

It isn't about whether a symbol *is* a number, but whether the name contains a number in it. For example, with yours or my patch a search for "2" will match a function named "txt2html".

By the way, is there a way to put Komodo customization in a separate file or something so they don't get lost at the next update?

The best way would be to write an extension that monkey-patches the relevant Komodo method. That isn't straightforward tho. I wonder if Komodo could grow a "My Tweaks" extension (or something like that) that is in every user's extensions area for just local customizations. Then Komodo tries to help the user do the right thing for customizations like this.

Trent

--
Trent Mick
trentm at activestate.com

Re: Change in 'Open Recent Projects and Files'?

2008-11-10T02:54:27Z

Just to follow up on this, it worked fine after a reboot.

Rob

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: Changing the behavior of the "Section List" box

2008-11-07T15:21:16Z

Mathieu Longtin wrote:
> Here, sorry, this is not a real patch diff, I just overwrote the original.
> I'm leaving the priority as is, it's doubtful any symbol will be a
> number, since most languages require identifier to start with a letter
> or underscore.

It isn't about whether a symbol *is* a number, but whether the name
contains a number in it. For example, with yours or my patch a search
for "2" will match a function named "txt2html".

> By the way, is there a way to put Komodo customization in a separate
> file or something so they don't get lost at the next update?

The best way would be to write an extension that monkey-patches the
relevant Komodo method. That isn't straightforward tho. I wonder if
Komodo could grow a "My Tweaks" extension (or something like that) that
is in every user's extensions area for just local customizations. Then
Komodo tries to help the user do the right thing for customizations like
this.

Trent

--
Trent Mick
trentm at activestate.com
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: Changing the behavior of the "Section List" box

2008-11-07T12:59:59Z

Here, sorry, this is not a real patch diff, I just overwrote the original.
I'm leaving the priority as is, it's doubtful any symbol will be a number, since most languages require identifier to start with a letter or underscore.

By the way, is there a way to put Komodo customization in a separate file or something so they don't get lost at the next update?

    // Determine the line to jump to, if any.
    var line = -1; // -1 means no line to jump to
+    var view = ko.views.manager.currentView;
    if (this._sectionSelectedIndex == -1) {
        // This means a selection was NOT made from the popup list. I.e.
        // <Enter> was hit in the textbox with no selection in the popup
        // list. Use the first match.
        if (textbox.controller.matchCount) {
            line = Number(textbox.controller.getCommentAt(0));
+        } else if ( textbox.value.match(/^([+-]?)(\d+)$/) ) {
+            // $1 and $2 don't seem to work.
+            var [tmp,plusMinus,lineNo] = textbox.value.match(/^([+-]?)(\d+)$/);
+            if ( plusMinus == '+' ) {
+                line = view.scimoz.lineFromPosition(view.scimoz.currentPos)+lineNo;
+            } else if ( plusMinus == '-' ) {
+                line = view.scimoz.lineFromPosition(view.scimoz.currentPos)-lineNo;
+                if ( line < 0 ) { line = 1 }
            } else {
                line = lineNo;
            }
        } else {
            ko.statusBar.AddMessage("no sections match '"+textbox.value+"'",
                                    "sections", 3000, true);
        }
    } else {

--
Mathieu Longtin
1-514-803-8977

On Fri, Nov 7, 2008 at 2:09 PM, Trent Mick <trentm@...> wrote:

Mathieu Longtin wrote:

Hi,

I'd like to change the behavior of the section list box so that entering a number would jump me to that line.

I have searched everywhere in the code, but couldn't find the callbacks for that text box.

Can you point me in the right direction? Thanks

I'll try to point you in the right direction, though I'm not sure it will be easy. :) That textbox is hardwired to talk in terms of sections and not line numbers. Still, it is all hackable...

Most of the UI control for that textbox is in statusbar.js inside the komodo.jar file. Any of the methods with "section" in the name pertain to that part of the statusbar. In particular I think you may want to tweak "sectionTextEntered".

... okay, that was fun. Here is a patch that will do it:

------------

--- statusbar.js (revision 24721)
+++ statusbar.js (working copy)
@@ -845,9 +845,11 @@
if (this._sectionSelectedIndex == -1) {
// This means a selection was NOT made from the popup list. I.e.
// <Enter> was hit in the textbox with no selection in the popup
- // list. Use the first match.
+ // list. Use the first match or, if it is a number, that line number.
if (textbox.controller.matchCount) {
line = Number(textbox.controller.getCommentAt(0));
+ } else if (!isNaN(textbox.value)) {
+ line = parseInt(textbox.value);
} else {
ko.statusBar.AddMessage("no sections match '"+textbox.value+"'",
"sections", 3000, true);

------------

Note that I put the is-it-a-number check after the check for a match. This means that entering a value of say, "1" will jump to the first matching section name with "1" in it, if there is one. Only if the entered string is a number and doesn't match any section names will it jump to that line number.

If we want line number to always win (even if it matches a section), then the isNaN check would have to be first there.

Todd: you opinion on just adding this? Too subtle overloading of that textbox? Nice way to avoid the goto-line dialog?

Aside: Note that the current goto-line dialog also handling strings like "-10" for relative line movements. That could be added here too.

Cheers,
Trent

--
Trent Mick
trentm at activestate.com

Re: Changing the behavior of the "Section List" box

2008-11-07T11:06:13Z

Mathieu Longtin wrote:
> Hi,
>
> I'd like to change the behavior of the section list box so that entering
> a number would jump me to that line.
>
> I have searched everywhere in the code, but couldn't find the callbacks
> for that text box.
>
> Can you point me in the right direction? Thanks

I'll try to point you in the right direction, though I'm not sure it
will be easy. :) That textbox is hardwired to talk in terms of sections
and not line numbers. Still, it is all hackable...

Most of the UI control for that textbox is in statusbar.js inside the
komodo.jar file. Any of the methods with "section" in the name pertain
to that part of the statusbar. In particular I think you may want to
tweak "sectionTextEntered".

... okay, that was fun. Here is a patch that will do it:

------------

> --- statusbar.js (revision 24721)
> +++ statusbar.js (working copy)
> @@ -845,9 +845,11 @@
> if (this._sectionSelectedIndex == -1) {
> // This means a selection was NOT made from the popup list. I.e.
> // <Enter> was hit in the textbox with no selection in the popup
> - // list. Use the first match.
> + // list. Use the first match or, if it is a number, that line number.
> if (textbox.controller.matchCount) {
> line = Number(textbox.controller.getCommentAt(0));
> + } else if (!isNaN(textbox.value)) {
> + line = parseInt(textbox.value);
> } else {
> ko.statusBar.AddMessage("no sections match '"+textbox.value+"'",
> "sections", 3000, true);

------------

Note that I put the is-it-a-number check after the check for a match.
This means that entering a value of say, "1" will jump to the first
matching section name with "1" in it, if there is one. Only if the
entered string is a number and doesn't match any section names will it
jump to that line number.

If we want line number to always win (even if it matches a section),
then the isNaN check would have to be first there.

Todd: you opinion on just adding this? Too subtle overloading of that
textbox? Nice way to avoid the goto-line dialog?

Aside: Note that the current goto-line dialog also handling strings like
"-10" for relative line movements. That could be added here too.

Cheers,
Trent

--
Trent Mick
trentm at activestate.com
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Komodo IDE and Edit 5.0.1 released

2008-11-06T13:33:15Z

Komodo IDE and Komodo Edit 5.0.1 have been released. You can download
them directly here:

http://www.activestate.com/Products/komodo_ide/index.mhtml
http://www.activestate.com/Products/komodo_ide/komodo_edit.mhtml

This is a bug fix release to resolve a few important issues in 5.0.0
(released two days ago) for some users. Full details are here in the
release notes:

http://docs.activestate.com/komodo/5.0/releases/ide.html#bug_fixes-5.0.1

Komodo's auto-update system should notice the update within the next
day, or you can use "Help > Check for Updates...".

As ever, we welcome your feedback:

email: http://listserv.activestate.com/mailman/listinfo/komodo-discuss
bugs: http://bugs.activestate.com/enter_bug.cgi?product=Komodo
forums: http://community.activestate.com/products/Komodo

Cheers,
Trent

--
Trent Mick
Komodo Lead
trentm at activestate.com

_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Changing the behavior of the "Section List" box

2008-11-06T11:54:21Z

Hi,

I'd like to change the behavior of the section list box so that entering a number would jump me to that line.

I have searched everywhere in the code, but couldn't find the callbacks for that text box.

Can you point me in the right direction? Thanks

--
Mathieu Longtin
1-514-803-8977

_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Change in 'Open Recent Projects and Files'?

2008-11-05T10:37:31Z

In Komodo Edit 5 if I click no to the 'Open Recent Projects and Files'
question the section on the start page which lists recent files doesn't
open. In earlier versions I would still get the list on the start page
even if I didn't want to actually open up the files. Is this change
deliberate, or perhaps just me?

Rob

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: Tcl remote debugger and spawnpoints

2008-11-05T00:44:52Z

Hi,

Here is the detailed information.

There are to files: parent.tcl and child.tcl

=== parent.tcl ===
proc spawn {cmd args} {
puts [exec [info nameofexecutable] $cmd $args]
}

puts "PARENT STARTED"
spawn child.tcl
puts "PARENT FINISHED"
=== child.tcl ====
puts "CHILD STARTED"
puts "CHILD FINISHED"
==================

The contents of the files is based on the
http://docs.activestate.com/tdk/5.0/Debugger.html#mult_processes

The command line used to start debugger is (all on the same line):
C:\TCL-Debug\5\dbgp_tcldebug.exe
-dbgp 192.168.3.135:10000
-app-shell C:\Tcl85\bin\tclsh85.exe
-ide-key dbgp_1225872443074
-log -logfile C:\TCL-Debug\log
-app-file C:\home\tcl-spawnpoints\parent.tcl --

DBGP request:
spawnpoint_set -s enabled -n 6 -i 68 -f
file:///C:/home/tcl-spawnpoints/parent.tcl

DBGP response:
<?xml version="1.0" encoding="UTF-8" ?>
<response xmlns="urn:debugger_protocol" command="spawnpoint_set"
transaction_id="68" state="enabled" id="0" />

After that:
run -i 70

response:
- a few stream/OUTPUT packets, followed by
<?xml version="1.0" encoding="UTF-8" ?>
<response xmlns="urn:debugger_protocol" command="run"
transaction_id="70" status="stopping" reason="ok" />

Debuggger log:
The whole log file size is about 200kb, the spawnpoint handling part is:

...
LOG(timing,3271527680): HandleNubEvent ENTER
LOG(message,3271527680): reading 105 bytes
LOG(message,3271527680): got (105): 'SPAWN_RQ {{0 {} global} {0 {1 6 {97
16}} source C:/home/tcl-spawnpoints/parent.tcl}} {} {spawn child.tcl}'
LOG(timing,3271527680): HandleNubEvent SPAWN_RQ
debug | appState = stopped (traced, sync'd)
LOG(timing,3271527680): DeliverEvent stdin ()
debug | appState = running (traced, sync'd)
LOG(message,3271527680): sent: len=117 'SPAWN_ACK alex
{::dbgp::client::Spawn request {spawn child.tcl} ::client}
C:/TCL-Debug/5/appLaunch.tcl {} tcldbgp2472'
LOG(timing,3271542680): HandleNubEvent ENTER
...

Output:
PARENT STARTED
PARENT FINISHED

Output if there is no spanwpoint or if spawnpoint is disabled:
PARENT STARTED
CHILD STARTED
CHILD FINISHED
PARENT FINISHED

So it looks like the new process is not started if there is a spawnpoint.

Also, it should made subsequent DBGP connection from the child process,
but it also does not happen.

It should be enough information to reproduce the issue. If you need more
information - please let me know.

Thanks,
Alex

Jeff Hobbs wrote:

> Alex Panchenko wrote:
>> I am not sure what mailing list should be used for my question, so I
>> will post to all related ones.
>>
>> I am interested in the DBGP support of the spawnpoints. Does tcl
>> remote debugger support spawnpoints?
>>
>> At the moment Komodo IDE does not allow me even to setup spawnpoints
>> when remote debugger is attached.
>> I can debug the same code with spawnpoint using Tcl Dev Kit Debugger,
>> but it looks like it uses proprietary protocol to communicate with
>> the launched process.
>
> Yes, the TDK Debugger uses a different Tcl-oriented protocol as it
> preceded dbgp and was designed just for Tcl. The debugger backends
> between TDK and Komodo use the same debugging core for Tcl though.
> There handling of spawnpoints will vary as the protocol allows, but as
> it is the debugging core with the support, it should be "the same".
>
>> Back to the DBGP: I can send spawnpoint_set command (and verify the
>> result with spawnpoint_list), but when the process reaches the
>> specified line nothing happens. Should I use some undocumented
>> commands to make it work, is it a bug or a missing feature?
>>
>> My configuration is
>> - Windows XP
>> - Tcl 8.4
>> - latest tcl remote debugger
>
> In my testing, one obvious variation that I noted was that TDK will
> report invalid spawnpoint lines (lines not recognized by the debugger
> as allowable spawn points). In TDK, a dialog will show to indicate
> this, but I received no such feedback from Komodo.
>
> Currently only [exec], [spawn] and [thread::create] are recognized
> spawn point generators. This is a hardcoded core list (unless you
> extend with .pdx files), and I noticed one quirk about this ...
> exp_spawn was not recognized, whereas spawn was. This is something we
> need to correct.
>
> In any case, that may be what you hit. You are using the correct dbgp
> commands though. Can you describe in more detail the tests you are
> using? Have you tried running dbgp_tcldebug with -log (activate
> logging) and -logfile myfile.txt (redirect log from stdout to file)?
> That should provide more detailed information.
>
> Regards,
>
> Jeff

Re: Komodo IDE 5.0 is Here

2008-11-04T11:40:17Z

Issac Goldstand wrote:
> FYI, Komodo 5 not showing up in "Check for updates" yet

That is correct. For a couple of reasons, Komodo's auto-update server
doesn't offer the update for a major version bump:

1. For Komodo IDE it is a paid upgrade, so you need to purchase a
license key first.

2. The default install directory is different (except on Mac OS X where
putting a version number in the ".app" name seems to be quite uncommon).
We've found that on Windows and Linux, at least, many users prefer to
have separate installations of major Komodo versions for a little while
to feel things out and get used to the differences -- a major upgrade of
Komodo can feel quite different. Having the installer by default put
those in separate directories has shown to cause less confusion.

We've attempted to notify people of Komodo 5 availability inside Komodo
via the Start Page "What's New" section.

Cheers,
Trent

--
Trent Mick
trentm at activestate.com
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: [Komodo-beta] Komodo IDE 5.0 is Here

2008-11-04T07:50:23Z

Hansen, Mike wrote:

> Correct me if I'm wrong, but you have to upgrade(purchase) major
> versions of Komodo. You can't get it using "Check for updates".

And for all on this list who got a free license 4 as beta-testers: Right
now upgrading from a paid version 3 to 5 isn't working (just mailed
Active State if there's a way anyhow).

Rudi
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Komodo IDE 5.0 Released Today

2008-11-04T06:52:16Z

Good News! Komodo IDE 5.0 is now available.

****************************************
What's New in Komodo IDE 5.0
****************************************
Share the joy (and the workload) with Komodo IDE 5.0's new and improved
features for team development.

* Shared code: With new support for the Git, Mercurial (hg), and Bazaar
distributed version control systems (or the already supported
Subversion, Perforce, and CVS), you can share your code with whichever
SCC system you choose. And smart cross-SCC system checkout wizardry
makes it easier to get to work on shared repositories.

* Shared beauty: Consistent formatting improves code readability and
maintainability in a team. Easily hook external code formatting tools
(like PHP Beautifier, Perltidy, and astyle) into Komodo IDE 5.0 or add
tighter integration via an extension.

* Shared speed: Komodo IDE 5.0 is now built on the Mozilla 1.9 codebase
(the same codebase as Firefox 3) and Python 2.6, so it's speedier,
prettier (particularly the more native look on OS X), and has new
features to aid in stability.

* And more, of course: Like multiple top-level windows, slicker UIs for
tabs and sidebars.... Check out the Komodo IDE 5.0 documentation for all
the details: http://docs.activestate.com/komodo/5.0/

****************************************
Buy Now & Save
****************************************
Check out the great deals on upgrades to Komodo IDE 5.0, new licenses,
and 5-packs for small teams:
http://www.activestate.com/Products/komodo_ide/sale.mhtml

Hurry! The sale ends December 23, 2008.

****************************************
Try Komodo IDE 5.0
****************************************
Download a free 21-day trial of Komodo IDE 5.0 and see the new features
in action:
http://www.activestate.com/Products/komodo_ide/latest_release.mhtml

Enjoy!

--

Erin Williams
Developer Marketing & Communications
ActiveState Software
t: 778.786.1108
e: erinw@...

Read the latest news and notes from ActiveState at
http://planet.activestate.com/.

_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: Komodo IDE 5.0 is Here

2008-11-04T06:42:07Z

FYI, Komodo 5 not showing up in "Check for updates" yet

ActiveState wrote:
>
>
> Hi there,
>
>
>
> Good news: the new Komodo IDE 5.0 has just been released! Check out the
> new and improved features
[snip]
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: Tcl remote debugger and spawnpoints

2008-11-02T15:57:19Z

Alex Panchenko wrote:

> I am not sure what mailing list should be used for my question, so I
> will post to all related ones.
>
> I am interested in the DBGP support of the spawnpoints. Does tcl remote
> debugger support spawnpoints?
>
> At the moment Komodo IDE does not allow me even to setup spawnpoints
> when remote debugger is attached.
> I can debug the same code with spawnpoint using Tcl Dev Kit Debugger,
> but it looks like it uses proprietary protocol to communicate with the
> launched process.

Yes, the TDK Debugger uses a different Tcl-oriented protocol as it
preceded dbgp and was designed just for Tcl. The debugger backends
between TDK and Komodo use the same debugging core for Tcl though.
There handling of spawnpoints will vary as the protocol allows, but as
it is the debugging core with the support, it should be "the same".

> Back to the DBGP: I can send spawnpoint_set command (and verify the
> result with spawnpoint_list), but when the process reaches the specified
> line nothing happens. Should I use some undocumented commands to make it
> work, is it a bug or a missing feature?
>
> My configuration is
> - Windows XP
> - Tcl 8.4
> - latest tcl remote debugger

In my testing, one obvious variation that I noted was that TDK will
report invalid spawnpoint lines (lines not recognized by the debugger as
allowable spawn points). In TDK, a dialog will show to indicate this,
but I received no such feedback from Komodo.

Currently only [exec], [spawn] and [thread::create] are recognized spawn
point generators. This is a hardcoded core list (unless you extend with
.pdx files), and I noticed one quirk about this ... exp_spawn was not
recognized, whereas spawn was. This is something we need to correct.

In any case, that may be what you hit. You are using the correct dbgp
commands though. Can you describe in more detail the tests you are
using? Have you tried running dbgp_tcldebug with -log (activate
logging) and -logfile myfile.txt (redirect log from stdout to file)?
That should provide more detailed information.

Regards,

Jeff
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss

Re: DBGPHideChildren variable

2008-10-31T14:16:04Z

This is a known bug: http://bugs.activestate.com/show_bug.cgi?id=64497

It's a variable used internally by the debugger engine,
and it's bleeding into the list of globals, and locals at
the top-level frame.

- Eric

FUJINAKA Tohru wrote:

> Hi,
>
> In the Python remote debugging session, there are a variable
> named DBGPHideChildren in Locals and Globals context.
>
> Question:
> a. what is the purpose of the variable?
> b. is useful for debugger user? will they manipulate?
> c. there are other variables in common.py of dbgp library.
> will they be shown in a certain condition?
>
> Thanks in advance
>

DBGPHideChildren variable

2008-10-31T00:05:35Z

Hi,

In the Python remote debugging session, there are a variable
named DBGPHideChildren in Locals and Globals context.

Question:
a. what is the purpose of the variable?
b. is useful for debugger user? will they manipulate?
c. there are other variables in common.py of dbgp library.
will they be shown in a certain condition?

Thanks in advance

--
FUJINAKA Tohru <fujinaka.tohru@...>

_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@...
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss