This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
[BC] Patch: FYI: avoid crash generating debug info
- From: Tom Tromey <tromey at redhat dot com>
- To: Java Patch List <java-patches at gcc dot gnu dot org>
- Cc: Gcc Patch List <gcc-patches at gcc dot gnu dot org>
- Date: 24 Nov 2004 16:50:42 -0700
- Subject: [BC] Patch: FYI: avoid crash generating debug info
- Reply-to: tromey at redhat dot com
I'm checking this in on the BC branch.
I've had this in my tree for quite a while. Andrew wrote it, it is a
bug fix that is needed when compiling jar files. Without this you
can get compiler crashes when compiling certain jar files. I'm
checking it in since I needed it to make the BC->trunk merge work
correctly.
Tom
Index: ChangeLog
from Andrew Haley <aph@redhat.com>
* jcf-parse.c (parse_class_file): Set file_start_location.
Index: jcf-parse.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/java/jcf-parse.c,v
retrieving revision 1.158.4.10
diff -u -r1.158.4.10 jcf-parse.c
--- jcf-parse.c 3 Nov 2004 00:10:58 -0000 1.158.4.10
+++ jcf-parse.c 24 Nov 2004 23:50:08 -0000
@@ -824,6 +824,7 @@
java_layout_seen_class_methods ();
input_location = DECL_SOURCE_LOCATION (TYPE_NAME (current_class));
+ file_start_location = input_location;
(*debug_hooks->start_source_file) (input_line, input_filename);
/* Currently we always have to emit calls to _Jv_InitClass when