Eclipse pb avec le debug + pb CPU

Bonjour,

Je vous contacte parce que je travaille sur une application dont le volume de données est non négligeable mais pas trop costaud non +. Il y a pas mal de traitements..
Quand je mets en mode debug sous eclipse 3.1

(je sais c'est pas la derniere version à jour mais c'est celle qu'on utilise au taf.
Notre application existe depuis 2003 et ils ne veulent pas changer de version parce qu'ils ont peur d'eventuels pbs de compatibilité et aussi parce que l'application est une appli sensible , ils veulent pas trop la bouger pour le moment).

Si vous avez des infos sur les differences entre les versions depuis la 3.1 merci d'avance.veuillez ne pas m'envoyer la reference du site http://www.eclipsetotale.com/ mais d'être assez précis .).

Bref, je bosse donc sous eclipse 3.1 et mon pc est un amd Athlon(tm) 64X2 Dual Core Processor 3800+,2GHz ,et 2GO de RAM.
Et quand je suis en mode debug, mon application utilise 90% voire 100% de mon cpu alors que quand je suis en mode Excecution , ça roule tranquillement.
C'est pas un pb de points d'arrêts, je les ai retirés.(j'ai 2 points d'arrets: un au depart , et un à la fin du traitement j'ai fait ça pour comprendre si c'etait bien le mode debug qui bloquait)

Avez une idée?
Cordialement,
tototata.

Bonjour,

Pour la compatibilité entre Eclipse 3.3 et les anciennes versions, j'ai ceci :

Citation:

---

Compatibility of Release 3.3 with 3.2

Eclipse 3.3 is compatible with Eclipse 3.2.

API Contract Compatibility: Eclipse SDK 3.3 is upwards contract-compatible with Eclipse SDK 3.2 except in those areas noted in the Eclipse 3.3 Plug-in Migration Guide . Programs that use affected APIs and extension points will need to be ported to Eclipse SDK 3.3 APIs. Downward contract compatibility is not supported. There is no guarantee that compliance with Eclipse SDK 3.3 APIs would ensure compliance with Eclipse SDK 3.2 APIs. Refer to Evolving Java-based APIs for a discussion of the kinds of API changes that maintain contract compatibility.

Binary (plug-in) Compatibility: Eclipse SDK 3.3 is upwards binary-compatible with Eclipse SDK 3.2 except in those areas noted in the Eclipse 3.3 Plug-in Migration Guide . Downward plug-in compatibility is not supported. Plug-ins for Eclipse SDK 3.3 will not be usable in Eclipse SDK 3.2. Refer to Evolving Java-based APIs for a discussion of the kinds of API changes that maintain binary compatibility.

Source Compatibility: Eclipse SDK 3.3 is upwards source-compatible with Eclipse SDK 3.2 except in the areas noted in the Eclipse 3.3 Plug-in Migration Guide . This means that source files written to use Eclipse SDK 3.2 APIs might successfully compile and run against Eclipse SDK 3.3 APIs, although this is not guaranteed. Downward source compatibility is not supported. If source files use new Eclipse SDK APIs, they will not be usable with an earlier version of the Eclipse SDK.

Workspace Compatibility: Eclipse SDK 3.3 is upwards workspace-compatible with Eclipse SDK 3.2 unless noted. This means that workspaces and projects created with Eclipse SDK 3.2, 3.1 or 3.0 can be successfully opened by Eclipse SDK 3.3 and upgraded to a 3.3 workspace. This includes both hidden metadata, which is localized to a particular workspace, as well as metadata files found within a workspace project (e.g., the .project file), which may propagate between workspaces via file copying or team repositories. Individual plug-ins developed for Eclipse SDK 3.3 should provide similar upwards compatibility for their hidden and visible workspace metadata created by earlier versions; 3.3 plug-in developers are responsible for ensuring that their plug-ins recognize 3.2, 3.1, 3.0, 2.1, and 2.0 metadata and process it appropriately. User interface session state may be discarded when a workspace is upgraded. Downward workspace compatibility is not supported. A workspace created (or opened) by a product based on Eclipse 3.3 will be unusable with a product based an earlier version of Eclipse. Visible metadata files created (or overwritten) by Eclipse 3.3 will generally be unusable with earlier versions of Eclipse.

Non-compliant usage of API's: All non-API methods and classes, and certainly everything in a package with "internal" in its name, are considered implementation details which may vary between operating environment and are subject to change without notice. Client plug-ins that directly depend on anything other than what is specified in the Eclipse SDK API are inherently unsupportable and receive no guarantees about compatibility within a single release much less with earlier releases. Refer to How to Use the Eclipse API for information about how to write compliant plug-ins.
Compatibility of Release 3.3 with 3.2, 3.1, 3.0, 2.1 and 2.0

Since Eclipse 3.3 is compatible with Eclipse 3.2, 3.1, 3.0, 2.1 and 2.0 in most regards, and Eclipse 3.3 is compatible with 3.2, it follows that 3.3 is also compatible with 3.2, 3.1, 3.0, 2.1 and 2.0 in most aspects. If you are upgrading directly from 3.1, 3.0, 2.1 or 2.0, refer also to the Eclipse 3.1 Plug-in Migration Guide and the Eclipse 3.2 Plug-in Migration Guide for problems areas.

---

Sinon pour le debug, je ne vois pas trop... C'est un peu normal si votre application consomme un peu plus mais taper du 90 - 100% ça me paraît un peu bizarre !

Pour information, il y a un forum Eclipse dédié !

Bonne journée,
Mathieu