This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See crosstool-NG for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 7 Sep 2012, aras.vaichas@gmail.com wrote: > I am having trouble debugging pthreads on my target. I am not sure > what the cause is, but I suspect it could be either my kernel or my > libraries. It seems that you need symbols to debug threads. I guess that gdb is looking for variables to determine what threads/stacks are where. It cann't seem to get back traces without symbols in the 'libc', etc. Have you stripped everything before you put it on your target? http://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html I found that on my ARM target, I could strip the libraries and use '--add-gnu-debug-link' method. I then can transfer the '.debug' files when I have an issue and gdb will read them and suddenly, I can use the pthread facility. ...probably not a CTNG issue. hth, Bill Pringlemeir. -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |