As this page evolves and grows, the content contained herein, will be refactored somewhere within the GCJ subject area.

GCJ Mailing List Chronological Digest

*AWT* - NH ran into a few issues building his AWT-based application with GCJ: problems with FileDialog, canvas repainting, missing mouse events, and others. TF replies that some bugs are in progress, some bugs are fixed, the remaining identified bugs need PRs. TF concludes with some suggestions on debugging. NH replies with 10 PR submissions (thank you!). MW chimes in with examples of working GCJ-compiled AWT apps. In addition, MW says to expect a merge of current ui work to the gcc trunk before Feb 24 (the GCC branch for 4.0 release). NH follows up with a couple more PRs and a last word (for now).
*unwinding* - MA asked about getting a thread dump from a running GCJ application. AH replied that it would be hard to do, instead use gdb: essentially because unwind information is not generated for all instructions (on certain architectures), and without that it is difficult to trace the stack. MN suggests a tip for dumping heaps (which has an outstanding defect), but this doesn't help in dumping stacks.
*parsing* - RM asks about when EXPR_WITH_FILE_LOCATION tree nodes should be generated while parsing source code. PB metioned that EWFL should go away in the future, in deference to USE_MAPPED_LOCATION. In any case, EWFL will obsoleted by GCJX).
*freebsd* - JWR had trouble running an application on FreeBSD 5.3 using a freebsd port of gcc3.4.4.

GCJ Mailing List Topical Digest

Controlling the garbage collector (GC) at runtime? (MN 02/02/2005).
Controlling heap-size growth; strategies for user-controlled collector; collection strategies by target; linux bug from optimistic memory allocation
1. related: Setting memory-chunk-size claimed when free-memory approaches zero? (MN 11/24/2004)

OOM ||

NPE ||

COW ||

PR ||

PIC||