[ale] GDB problem on RH AS 3

[pras at cycloeastern.com]

You might be onto something here !!!

#0  0x02c399d0 in clone () from /lib/tls/libc.so.6
#1  0x002a68d7 in do_clone () from /lib/tls/libpthread.so.0
#2  0x002a6526 in create_thread () from /lib/tls/libpthread.so.0
#3  0x002a5f87 in pthread_create@@GLIBC_2.1 () from /lib/tls/libpthread.so.0
#4  0x002a601c in pthread_create at GLIBC_2.0 () from /lib/tls/libpthread.so.0
#5  0x002edf3a in VISThread::_create_thread () from /usr/BDP/lib/libvport_r.so
#6  0x002ee0bc in VISThread::run () from /usr/BDP/lib/libvport_r.so
#7  0x013f9588 in VISManager::cleanup () from /usr/BDP/lib/liborb_r.so
#8  0x013fa063 in VISManager::sig_handler () from /usr/BDP/lib/liborb_r.so
#9  0x013fa4a1 in VISThreadSignal::begin () from /usr/BDP/lib/liborb_r.so
#10 0x002ec749 in VISThread::_start () from /usr/BDP/lib/libvport_r.so
#11 0x002a5dec in start_thread () from /lib/tls/libpthread.so.0
#12 0x02c39a2a in clone () from /lib/tls/libc.so.6

Here is my stack.

It appears as though pthreads use close as well ?



On Tue, Apr 12, 2005 at 12:21:14PM -0400, Christopher Fowler wrote:
> Are you using clone() to do threads.  A friend and I had a similar
> problem last week.  However he just started his program and we
> chose to use pthreads instead of clone() directly.  When we did that
> He was able to debug the threads.  For some reason GDB would go stupid
> when we just used clone().  We did not have time to figure out why.
> 
> 
> On Tue, 2005-04-12 at 12:29, pras at cycloeastern.com wrote:
> > All,
> > 
> > I work for a company in that has started using Linux for one of its projects
> > that has traditionally in the past been running on all other big iron *nixes.
> > 
> > We just got our first build on RH Enterprise Linux AS release 3 (Taroon Update 4),
> > and gdb attemptys fail miserably.
> > 
> > Background info:
> > 
> > The product is written in C/C++ and is compiled with gcc 3.2.3
> > The gdb version is as follows:
> > GNU gdb Red Hat Linux (6.1post-1.20040607.52rh)
> > 
> > I am able to attach to a process and see the stack using backtrace or bt. frame command
> > works and even break command works.
> > 
> > 
> > When I try to do a 'cont', the server process which is supposed to execute continuously exists normally.
> > 
> > This is what I see
> > 
> > (gdb) cont
> > Continuing.
> > [New Thread -1245635664 (LWP 8226)]
> > [Thread -1220756560 (LWP 7953) exited]
> > 
> > Program exited normally.
> > (gdb)
> > 
> > 
> > Do you guys know what might be going wrong ?
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale

-- 
________________________________________________________________________
Prasanna Subash            | Is knowledge knowable?  If not, how do we
pras at cycloeastern.com      | know that? 
                           | 
                           | 
________________________________________________________________________