[Bug 19972] New: GDB confuses __libc_exit() and __libc__exit()

[bugzilla-daemon at ecoscentric dot com]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=19972

           Summary: GDB confuses __libc_exit() and __libc__exit()
           Product: eCos
           Version: unknown
          Platform: Other
        OS/Version: Other
            Status: RESOLVED
          Severity: normal
          Priority: low
         Component: Other
        AssignedTo: ebachalo at schuilenburg dot org
        ReportedBy: nobody at cygnus dot com
                CC: jifl at ecoscentric dot com


With sparclite-elf-gdb, GDB seems to be able to confuse
the functions __libc_exit() and __libc__exit() (which is
called from __libc_exit())

How-To-Repeat:
Using the "twothreads" example that comes with the eCos
distribution:

GNU gdb 4.17-ecos-98r1p5
[snip]
(gdb) c
Continuing.
Entering twothreads' cyg_user_start() function
Beginning execution; thread data is 0
Beginning execution; thread data is 1
Thread 0: and now a delay of 239 clock ticks
Program received signal SIGINT, Interrupt.
0x40126ec in idle_thread_main (data=0)
    at /home/jlarmour/ecc/ecc/kernel/current/src/common/thread.cxx:1146
(gdb) info threads
  4 thread 4  0x4012ff4 in Cyg_Scheduler::unlock_inner ()
    at /home/jlarmour/ecc/ecc/kernel/current/src/sched/sched.cxx:142
    Name: Thread B, State: sleeping, Priority: 4, 
  3 thread 3  0x4012ff4 in Cyg_Scheduler::unlock_inner ()
    at /home/jlarmour/ecc/ecc/kernel/current/src/sched/sched.cxx:142
    Name: Thread A, State: sleeping, Priority: 4, 
  2 thread 2  0x4012ff4 in Cyg_Scheduler::unlock_inner ()
    at /home/jlarmour/ecc/ecc/kernel/current/src/sched/sched.cxx:142
    Name: main, State: exited, Priority: 0, 
* 1 thread 1  0x40126ec in idle_thread_main (data=0)
    at /home/jlarmour/ecc/ecc/kernel/current/src/common/thread.cxx:1146
    Name: Idle Thread, State: running, Priority: 31, 
(gdb) thread 2
[Switching to thread 2]
#0  0x4012ff4 in Cyg_Scheduler::unlock_inner ()
    at /home/jlarmour/ecc/ecc/kernel/current/src/sched/sched.cxx:142
142                                                &next->stack_ptr );
(gdb) bt
#0  0x4012ff4 in Cyg_Scheduler::unlock_inner ()
    at /home/jlarmour/ecc/ecc/kernel/current/src/sched/sched.cxx:142
#1  0x4012344 in Cyg_Thread::exit ()
    at /local/disk5/ecc-obj/install/include/cyg/kernel/sched.inl:91
#2  0x401751c in __libc__exit (status=0)
    at /home/jlarmour/ecc/ecc/language/c/libc/current/src/stdlib/_exit.cxx:88
#3  0x4017510 in __libc__exit (status=0)
    at /home/jlarmour/ecc/ecc/language/c/libc/current/src/stdlib/exit.cxx:94
#4  0x401743c in main (argc=0, argv=0x401d798)
    at /home/jlarmour/ecc/ecc/language/c/libc/current/src/support/invokemain.cxx:87

So GDB simply displays the wrong function name, even
though it does get the filenames and line numbers correct.


---------------------------------------------------------------------------

Originator:
Jonathan Larmour

Organization:
cygnus

Audit-Trail:
Responsible-Changed-From-To: alexs->ebachalo 
Responsible-Changed-By: alexs 
Responsible-Changed-When: Tue Apr 27 06:00:30 PDT 1999 
Responsible-Changed-Why:  
Hi Eric 

A GDB problem thrown out be eCos QA. 
-- Alex

Unformatted:
Originator:  

page: www.cygnus.com/product/ecc-pr.html

Send_PR_form: Sent_from_www.cygnus.com

------- Additional Comments From alexs at ecoscentric dot com  2003-24-04 17:15 BST -------
Tools issue



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