Ticket #20 (closed defect: fixed)

Opened 5 years ago

Last modified 2 years ago

"written length does not match optimized length" with stabs enabled

Reported by: jlawson-yasm Assigned to: mu@tortall.net
Priority: P2 Milestone: 0.4.0
Component: Debug Format: stabs Version: other
Severity: normal Keywords:
Cc:

Description 

I've encountered this internal error when attempting to compile some source code with stabs 
debugging output enabled. 
 
INTERNAL ERROR at libyasm/bytecode.c, line 839: written length does not match optimized 
length 
Abort 
 
I am using a current CVS checkout dated today (20031019).  Command-line used was:   
 
yasm -f elf -m amd64 -p nasm -r nasm -g stabs plat/x86_64/x86ident.asm

Attachments

Change History

11/03/03 19:09:55 changed by jlawson-yasm 

Created an attachment (id=1)
offending source used to repro failure.

11/03/03 19:12:46 changed by jlawson-yasm 

Removing "-g stabs" from the command-line allows the assembly to succeed without problems.

11/04/03 11:55:54 changed by mu

  • owner changed from peter@tortall.net to mu@tortall.net.
  • component changed from core to debug format: stabs.
This is a stabs bug.  Taking ownership.

11/04/03 11:58:17 changed by mu

  • status changed from new to assigned.
Broken Fix in modules/dbgfmt/stabs/stabs-dbgfmt.c r1.5.  Only saving for
compatibility with the previous incorrect design in case we find cases where the
stabs n_value field is not 32 bits.

11/04/03 12:09:22 changed by mu

  • status changed from assigned to resolved.
  • resolution set to fixed.

11/04/03 12:09:23 changed by mu 

Fixed in modules/dbgfmts/stabs/stabs-dbgfmt.c r1.6 by removing 16-byte stab
support.  Apparently existing 64-bit systems use truncated 32-bit n_value
fields, and objdump -G appears to agree.  stabs-dbgfmt.c now matches this behavior.

Thanks, Jeff!  Your code should now work with stabs.  (As much as the stabs
debugging works, anyway.)

Add/Change #20 ("written length does not match optimized length" with stabs enabled)