Thanks Pablo,
It looks like that was the trick.
Frank
--- In Pablo González Bucchi <> wrote:
>
> You have to use the same sheared object lib. Set solib-absolute-prefix
> in gdb to point at the same libs that you use on your board, I
point to
> the nfs root directory as I boot my ts for development form a nfs
> server. With this I get passed the SIG32 and get to list all my
threads,
> take in mind that using gdbserver you will not get notifications of
> thread creation remotely, but if you do run "info threads" there all
there.
>
> Regards
>
> Pablo
>
> Frank Pagliughi wrote:
> > Thanks Mattieu,
> >
> > I saw the SIG32's and got past them in the way you describe. But once
> > the thread is created it doesn't show up in the thread list. (No
> > matter hos many threads you create it only shows the main thread). But
> > the thread does seem to run. Unless I insert a breakpoint into it.
> > Then I get the SIGTRAP and everything stops working. It's almost like
> > the debugger doesn't understand the pthread and thinks it's another
> > process.
> >
> > I'm doing remote debugging over TCP with gdbserver running on the
> > target. Version 6.4 of both.
> >
> > I suspect that it may be a problem with the way gdb or gdbserver is
> > compiled. But I do get the same result whether I'm running the command
> > line gdb on the host or Insight.
> >
> > I see the same problem posted at various places on the Web, but no
> > solution posted!
> >
> > Frank
> >
> >
> > --- In Matthieu Crapet <mcrapet@> wrote:
> >
> >> Greetings,
> >>
> >>> I've tested the C & C++ compilers, but not Java yet. Everything
seems
> >>> to work well, but I am unable to debug pthreads. When I create a new
> >>> thread the debugger doesn't see it, and if I set a breakpoint in the
> >>> thread I get a SIGTRAP and the debugger stops working.
> >>>
> >>>
> >> I can't say if it is similar, but I have already got this kind of
> >>
> > problem.
> >
> >> For me it was SIG32 (don't remember at all why [stripped
binary??] and
> >> when...) ; but I remember that I needed to ignore signals (occurs at
> >> each thread creation).
> >>
> >> (gdb) handle SIG32 nostop noprint pass
> >>
> >> I found also another method : you launch your program, and after you
> >> attach the PID with GDB (gdb --pid=)
> >>
> >> Hope it helps !
> >>
> >> Matthieu
> >>
> >>
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|