This is the mail archive of the gdb@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] |
Hi, The problem seems that GDB doesn't succeed in switching frame stack to access threads information. More precisely, in the switch_to_thread function we have: select_frame (get_current_frame (), 0); that doesn't select the correct frame. Even more deeper, this is the read_fp() function that at some point always return the same frame pointer (that is the one from the running thread) Can someone tell me how does read_fp() should work in order to get the correct frame pointer? There may be an bug in eCos (see a discussion about that on the eCos mailing list archives) and I would like to know at wich point in this process there is an interaction between gdb and the target. Thank you -- Fabrice Gautier fabrice_gautier@sdesigns.com > -----Original Message----- > From: Fabrice Gautier [mailto:Fabrice_Gautier@sdesigns.com] > Sent: Wednesday, August 23, 2000 12:54 PM > To: GDB (E-mail) > Subject: Multi-thread debugging with eCos on i386 pc platform > > > Hi, > > I'm trying to debug a multithreaded eCos program. I'm using gdb 5 for > cygwin. > > I can see the threads created but I can't see where is the instruction > pointer for each thread nor can i change thread. > > The problem may be in the eCos stub code but I can't find > where and I would > like to know from what struture or from where does gdb know > the position of > each thread? > > Thanks you > > -- > Fabrice Gautier > fabrice_gautier@sdesigns.com >
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |