From: "Paul Sulistio" <psulistio@hotmail.com>
To: gdb@sources.redhat.com
Subject: corelow.c
Date: Fri, 14 Sep 2001 19:24:00 -0000 [thread overview]
Message-ID: <F159DLnuAdmdFcOvZFL000102fa@hotmail.com> (raw)
Hi,
I am porting info threads capabilities from FreeBSd to NetBSD 1.4.1 (not
support info thread) on i386 machine using gdb4.18 I am successfully ported
this but only when debugging the running threads.
When I tried to debug the core dump, i have problem
----------------------------------------------------
in corelow.c
-add_to_thread_list ()
if(strncmp(bfd_section_name(abfd,asect),".reg/",5)!=0)
return;
when i extract the value of (asect)->name always gives me .stack
or .data instead of .reg/
Does anyone know why I get .stack and .data instead of .reg or .reg/ ?
Any help would be greatly appreciated.
Thanks,
-paul
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
next reply other threads:[~2001-09-14 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 19:24 Paul Sulistio [this message]
2001-09-14 19:31 ` corelow.c Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F159DLnuAdmdFcOvZFL000102fa@hotmail.com \
--to=psulistio@hotmail.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox