This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/46618] New: UNKNOWN_LOCATION => bus error
- From: "jay.krell at cornell dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 23 Nov 2010 11:15:48 +0000
- Subject: [Bug debug/46618] New: UNKNOWN_LOCATION => bus error
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46618
Summary: UNKNOWN_LOCATION => bus error
Product: gcc
Version: 4.5.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: jay.krell@cornell.edu
I frequently see like this:
I don't know about this one, but generally it is because our frontend had used
UNKNOWN_LOCATION. I replace it with BUILTINS_LOCATION to fix it.
Can't UNKNOWN_LOCATION be acceptable?
(gdb) run
Starting program: /Users/jay/dev2/cm3/m3-sys/m3cc/AMD64_DARWIN-PA64_HPUX/cm3cg
-quiet -fPIC PA64_HPUX/TextCat.mc -g
Reading symbols for shared libraries +++. done
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
htab_hash_string (p=0x0) at ../../gcc-4.5/libiberty/hashtab.c:816
816 while ((c = *str++) != 0)
(gdb) bt
#0 htab_hash_string (p=0x0) at ../../gcc-4.5/libiberty/hashtab.c:816
#1 0x00268e9f in lookup_filename (file_name=0x0) at
../../gcc-4.5/gcc/dwarf2out.c:20124
#2 0x0028439d in add_dwarf_attr [inlined] () at
../../gcc-4.5/gcc/dwarf2out.c:16758
#3 0x0028439d in add_AT_file [inlined] () at
../../gcc-4.5/gcc/dwarf2out.c:7265
#4 0x0028439d in add_src_coords_attributes (die=0x0, decl=0x4132e050) at
../../gcc-4.5/gcc/dwarf2out.c:16758
#