public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/55468] New: Label value to incorrect destination
@ 2012-11-26  6:29 martin.girard5 at gmail dot com
  2012-11-26  6:30 ` [Bug c++/55468] " martin.girard5 at gmail dot com
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: martin.girard5 at gmail dot com @ 2012-11-26  6:29 UTC (permalink / raw)
  To: gcc-bugs


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55468

             Bug #: 55468
           Summary: Label value to incorrect destination
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: martin.girard5@gmail.com


This is a case of a label pointing to the wrong line. It is clear from looking
at the disassembly that the value of said label is bogus.

Look around line 31452. The sigtrap label points to line 31458. Instead, the
&&sigtrap label gives the address of line 31448, four lines above instead of
six lines below.

In the disassembly, one can see a movl instruction writing the address as a
function argument onto the stack, and said address is unmistakably the WSTOPSIG
macro four lines prior. As a result, the executable loops indefinitely upon
reaching this area, whereas it should be skipping the next block instead.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2024-03-16 17:56 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-11-26  6:29 [Bug c++/55468] New: Label value to incorrect destination martin.girard5 at gmail dot com
2012-11-26  6:30 ` [Bug c++/55468] " martin.girard5 at gmail dot com
2012-11-26  6:40 ` martin.girard5 at gmail dot com
2012-11-26  8:56 ` pinskia at gcc dot gnu.org
2024-03-16 17:56 ` pinskia at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).