[Bug nptl/6693] New: clone.S:thread_start() implementation causes an infinite _Unwind_Backtrace.

[Bug nptl/6693] New: clone.S:thread_start() implementation causes an infinite _Unwind_Backtrace.

[pluto at agmk dot net]

this is a forward from gcc bugzilla:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36568
afaics the glibc-2.8 is affected and there's
a patch provided in debian/ubuntu distro.
could you please verify and commit linked patch?

-- 
           Summary: clone.S:thread_start() implementation causes an infinite
                    _Unwind_Backtrace.
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
        AssignedTo: drepper at redhat dot com
        ReportedBy: pluto at agmk dot net
                CC: glibc-bugs at sources dot redhat dot com
GCC target triplet: x86_64-gnu-linux


http://sourceware.org/bugzilla/show_bug.cgi?id=6693

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

[Bug nptl/6693] clone.S:thread_start() implementation causes an infinite _Unwind_Backtrace.

[drepper at redhat dot com]

------- Additional Comments From drepper at redhat dot com  2008-08-13 05:21 -------
I see no problem with the current code:

$ ./a threaded
0x804886d handler+0x1a
0x11f400 __kernel_sigreturn+0x0
0x804888b crash+0x10
0x1ff20e clone+0x5e


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME


http://sourceware.org/bugzilla/show_bug.cgi?id=6693

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

[Bug nptl/6693] clone.S:thread_start() implementation causes an infinite _Unwind_Backtrace.

[pluto at agmk dot net]

------- Additional Comments From pluto at agmk dot net  2008-08-13 07:30 -------
(In reply to comment #1)
> I see no problem with the current code:
>
> $ ./a threaded
> 0x804886d handler+0x1a
> 0x11f400 __kernel_sigreturn+0x0
> 0x804888b crash+0x10
> 0x1ff20e clone+0x5e

which kernel/glibc/gcc/distribution you are using?

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=6693

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

[Bug nptl/6693] clone.S:thread_start() implementation causes an infinite _Unwind_Backtrace.

[pluto at agmk dot net]

------- Additional Comments From pluto at agmk dot net  2008-11-18 08:24 -------
(In reply to comment #1)
> I see no problem with the current code:
> 
> $ ./a threaded
> 0x804886d handler+0x1a
> 0x11f400 __kernel_sigreturn+0x0
> 0x804888b crash+0x10
> 0x1ff20e clone+0x5e

did you test it on the x86_64 architecture?
i'm asking because your logs shows 32-bits addresses
and the problem exist only on x86_64.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |


http://sourceware.org/bugzilla/show_bug.cgi?id=6693

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

[Bug nptl/6693] clone.S:thread_start() implementation causes an infinite _Unwind_Backtrace.

[schwab@linux-m68k.org]

http://sourceware.org/bugzilla/show_bug.cgi?id=6693

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WORKSFORME

--- Comment #4 from Andreas Schwab <schwab@linux-m68k.org> 2010-11-19 16:59:51 UTC ---
Not reproducible.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.