Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [Dltk-dev] Variables in the debugger that are shownasIndexedVariablePartition [0..99], [100..199] are after that filtered..

Hi Johan,

I've fixed JavaScript feature, so jsjdtdebugger is now included in
build. I've promoted integration build with debugger to Eclipse download
site.
> What is by the way the big difference between an Interpreter and the
> Debugging engine?
Main difference is what interpreters provide project buildpath information.
> Isnt that a one one relation?
In general interpreter and debugger are not related. Because we could
have debugger which is not require interpreter at all. For our cases we
have dependencies. For tcl ActiveState debugger require passing of tcl
interpreter executable as arguments, for Ruby we have debugger written
on Ruby itself.

Also we could have many interpreters. For each project we could choose
which interpreter to use. But for debuggers we have only one. And then
debug are started it could use projects interpreter.

Best regards,
Andrei Sobolev.

>
> johan
>  
>
> On Thu, Mar 27, 2008 at 1:47 PM, Johan Compagner <jcompagner@xxxxxxxxx
> <mailto:jcompagner@xxxxxxxxx>> wrote:
>
>     i will try to set something up
>     It is not a javascript project that you can just run
>     Because all the data comes from a remote debugger where it all
>     runs in. Not something dltk starts up
>
>     johan
>
>
>
>     On Thu, Mar 27, 2008 at 12:43 PM, timur <timur@xxxxxxxxx
>     <mailto:timur@xxxxxxxxx>> wrote:
>
>         Hi,
>
>          
>
>         I'm still have no idea how to reproduce this. Could you please
>         export your project and send it to me or create a short
>         example with this bug. Please mention where I should place
>         breakpoint and which variable become filtered.
>
>          
>
>         Thanks,
>
>         Tim
>
>         ------------------------------------------------------------------------
>
>         *From:* dltk-dev-bounces@xxxxxxxxxxx
>         <mailto:dltk-dev-bounces@xxxxxxxxxxx>
>         [mailto:dltk-dev-bounces@xxxxxxxxxxx
>         <mailto:dltk-dev-bounces@xxxxxxxxxxx>] *On Behalf Of *Johan
>         Compagner
>         *Sent:* Thursday, March 27, 2008 5:07 PM
>         *To:* DLTK Developer Discussions
>         *Subject:* Re: [Dltk-dev] Variables in the debugger that are
>         shownasIndexedVariablePartition [0..99],[100..199] are after
>         that filtered..
>
>          
>
>         turn of the functions
>         So that you dont see those
>
>         For example what i was looking at was a javabean (JSplitPane)
>         and those of loads of functions (setMinimumSize() etc)
>         And if you turn of those that you dont see them (you have to
>         toggle twice maybe at least in my place the filters are not by
>         default in sync need to look at that some more)
>         then of the 350 items you only see max 50 or something divided
>         over 4 partitions
>
>         johan
>
>         On Thu, Mar 27, 2008 at 11:40 AM, timur <timur@xxxxxxxxx
>         <mailto:timur@xxxxxxxxx>> wrote:
>
>         Hi Johan,
>
>          
>
>         Thank you for reporting. I've tried to reproduce your problem
>         using an array with 350 elements, but all was fine. There were
>         3 partitions with 100 elements each and one with 50. In
>         addition, I don't know what kind of filters you mean. May be I
>         misunderstood something. Please send me your snippet of code
>         and explain in more details what steps you've done to get this
>         error.
>
>          
>
>         Thanks,
>
>         Tim
>
>          
>
>         ------------------------------------------------------------------------
>
>         *From:* dltk-dev-bounces@xxxxxxxxxxx
>         <mailto:dltk-dev-bounces@xxxxxxxxxxx>
>         [mailto:dltk-dev-bounces@xxxxxxxxxxx
>         <mailto:dltk-dev-bounces@xxxxxxxxxxx>] *On Behalf Of *Johan
>         Compagner
>         *Sent:* Tuesday, March 25, 2008 7:33 PM
>         *To:* DLTK Developer list
>         *Subject:* [Dltk-dev] Variables in the debugger that are shown
>         asIndexedVariablePartition [0..99],[100..199] are after that
>         filtered..
>
>          
>
>         Hi,
>
>         i am trying to fix something but i cant immediately see how to
>         fix it
>
>         what i have is a variable in the debugger that has 350
>         children, that count is given to VariableContentProvider.
>         protected Object[] getValueChildren(IDebugElement parent,
>         IValue value, IPresentationContext context) throws CoreException
>
>         so that methods makes 4 IndexedVariablePartition
>
>         But when i open those in the ui. I dont see 99 items in each
>         of them no, sometimes only 5 or 6
>         this is because of the filters that seems to be applied after
>         the creation of the 4 IndexedVariablePartition ..
>
>         I dont know how Java does this, havent looked into that yet,
>         but at what point should the filter be applied?
>         The filter should run before or inside the getValueChildren()
>         method but i dont see any hook.
>
>         And ScriptValue cant call the filter because those classes
>         dont know anything about
>         VariableContentProvider/ModelContentProvider
>
>         So how is this supposed to work correctly?
>
>         johan
>
>
>         _______________________________________________
>         dltk-dev mailing list
>         dltk-dev@xxxxxxxxxxx <mailto:dltk-dev@xxxxxxxxxxx>
>         https://dev.eclipse.org/mailman/listinfo/dltk-dev
>
>          
>
>
>         _______________________________________________
>         dltk-dev mailing list
>         dltk-dev@xxxxxxxxxxx <mailto:dltk-dev@xxxxxxxxxxx>
>         https://dev.eclipse.org/mailman/listinfo/dltk-dev
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev
>   



Back to the top