This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gdbserver multithread ARM gdb-5.3/5.2


Hi 

I am new to gdbserver debugging. So I have got many queries...some of them
may be trivial..so forgive me for that...

I am trying to have a gdbserver for arm-linux target and x86/linux GDB host.
I have tried using the GDB-5.2.1 but that gdbserver doesn't seem to support
mutithreading.

Then I had downloaded the released GDB-5.3  through FTP from
sources.redhat.com.
Even the gdbserver of GDB-5.3 doesn't seem to work correctly for
multithreaded applications.
(gdb) info threads 

It only showed me the main thread ID and no other threads even if the test
application had many threads.
It even didn't stop at any breakpoint set on threads..

I think the released GDB -5.3 gdbserver is supposed to support
multithreading debugging for ARM targets properly.

Moreover, On the GDB-patches mailing list I could find some PATCH mail from
Danil Jacobowitz but it says something about "lin-thread.c"... but in
GDB-5.3 I couldn't find any such file.
Is it a totally new file or I have interpreted something incorrect..??

Is there any patch of gdbserver of gdb-5.3 or gdb-5.2 ??

To debug multithreaded applications, do I need to have the target arm-linux
shared libraries of libthread_db.so.1 on GDB host as well..??
If yes where to copy it..??

Has anyone supported GDB-5.2 gdbserver for thread debugging (remotely) ??

Can someone help me in making myself clear about the patches and GDB
versions for multithreaded debugging through gdbserver ??

Is it possible that I use the gdbserver of GDB-5.3 and the GDB host of
GDB-5.2 ??
I know it won't be recommended but how much is this feasible??


Waiting in anticipation

Thanks and regards
Vijay




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]