bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/994] section switch in function causes segfault


From: wilson at specifixinc dot com
Subject: [Bug gas/994] section switch in function causes segfault
Date: 8 Jun 2005 19:55:07 -0000

------- Additional Comments From wilson at specifixinc dot com  2005-06-08 
19:55 -------
Created an attachment (id=511)
 --> (http://sources.redhat.com/bugzilla/attachment.cgi?id=511&action=view)
Warn for section switch that corrupts unwind info.

This is my fix for the problem.  It does two things:
1) It emits a warning when this problem is detected.
tmp.s:21: Warning: Corrupted unwind info due to unsupported section switching
2) It tries to get the unwind info as correct as possible.  With Nick's patch,
the trailing body region has a length that is a large number computed from an
address returned by malloc.  With my patch, it is the correct number for this
testcase.  However, it is only the correct number if it is guaranteed that
there is no code after the .text.unlikely section switch.  This is not
guaranteed to be true in general.  So we still need the warning, or code to
check for this special case.  It isn't immediately obvious how to check for
this, or whether we can even check for it without changes to the machine
independent parts of the assembler, so I have made no attempt to write code for
this check.  I simply emit the warning unconditionally.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #510 is|0                           |1
           obsolete|                            |
         AssignedTo|unassigned at sources dot   |wilson at specifixinc dot
                   |redhat dot com              |com
             Status|REOPENED                    |ASSIGNED


http://sources.redhat.com/bugzilla/show_bug.cgi?id=994

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]