Thomas,
I uploaded the extension to
https://sourceforge.net/project/showfiles.php?group_id=182075&package_id=305572
The file is 
CoGrOO-AddOn-3.0.2-SNAPSHOT-bin.oxt<http://downloads.sourceforge.net/cogroo/CoGrOO-AddOn-3.0.2-SNAPSHOT-bin.oxt?use_mirror=>
Thank you!

Marcin,Thank you! The tutorial helped a lot! I could debug it.

But I still not able to find the crash problem.
Following you can see the logs generated by CoGrOO extension.

My steps to cause the crash was:
1. Created a new document.
2. Changed it to pt_BR
3. Entered a sentence with a grammar error: Fomos levados à crer.
4. Waited a few seconds, no automatic grammar checking (all log entries I
have was generated before I press F7)
5. Pressed F7 -> OOo crashed

The log is clear and easy to read. Something interesting is that the
method doProofreading was never called: no traces from that method and also
I inserted a breakpoint at the method's first line, and Eclipse never
stopped there.

Please help!

Thank you,
William

The log:
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
__getComponentFactory
FINER: ENTRY br.usp.pcs.lta.cogroo.ooointegration.Main
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getServiceNames
FINER: ENTRY
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getServiceNames
FINER: RETURN [com.sun.star.linguistic2.Proofreader,
br.usp.pcs.lta.cogroo.ooointegration.Main]
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
__getComponentFactory
FINER: RETURN com.sun.star.lib.uno.helper.fact...@dd20f6
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main Main
FINER: ENTRY 
com.sun.star.bridges.jni_uno.jni_pr...@e7b241[oid=29a296c;msci:unsafe[0];ea3c9e0959d4549984f4eb7f26c9c9f,
type=com.sun.star.uno.XComponentContext]
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main <init>
FINE: Called br.usp.pcs.lta.cogroo.ooointegration.Main
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main <init>
FINE: Will call Resources.init
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main Main
FINER: RETURN
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getImplementationName
FINER: ENTRY
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getImplementationName
FINER: RETURN br.usp.pcs.lta.cogroo.ooointegration.Main
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main getLocales
FINER: ENTRY
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main getLocales
FINER: RETURN pt_BR;
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main Main
FINER: ENTRY 
com.sun.star.bridges.jni_uno.jni_pr...@e7b241[oid=29a296c;msci:unsafe[0];ea3c9e0959d4549984f4eb7f26c9c9f,
type=com.sun.star.uno.XComponentContext]
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main <init>
FINE: Called br.usp.pcs.lta.cogroo.ooointegration.Main
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main <init>
FINE: Will call Resources.init
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main Main
FINER: RETURN
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getImplementationName
FINER: ENTRY
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getImplementationName
FINER: RETURN br.usp.pcs.lta.cogroo.ooointegration.Main
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main getLocales
FINER: ENTRY
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main getLocales
FINER: RETURN pt_BR;

Thank you!William


On Thu, Jan 8, 2009 at 3:43 PM, Marcin Miłkowski <[email protected]> wrote:

> CARLOS EDUARDO DANTAS DE MENEZES pisze:
>
>  Thomas,
>>
>> We are trying to debug new version of CoGrOO (3.0.2) but it sounds a
>> bit difficult.
>>
>> mene...@possante:~$ /opt/broffice.org3/program/soffice -writer
>> terminate called after throwing an instance of
>> 'com::sun::star::uno::RuntimeException'
>> sh: crash_report: not found
>>
>> Do you have any tip to easy this task?
>>
>
> Did you try debugging the Java code by attaching the debugger as described
> here? (I believe CoGrOO was using a small Java interface to call the
> standalone CoGrOO installation).
>
> See here:
>
> http://cedric.bosdonnat.free.fr/wordpress/?p=57
>
> This is really a very useful technique - if a grammar checker gets
> registered and called (on opening a text document), you will be able to set
> breakpoints and get into the code to see what happens. From my experience, I
> can tell you that most problems come from not setting the return values -
> they are not for fun, they cannot be null, they can be at most empty.
>
> Regards
> Marcin
>

Reply via email to