public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "raunaq at outlook dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/15349] gcore not implemented for AIX
Date: Fri, 19 Apr 2013 06:58:00 -0000 [thread overview]
Message-ID: <bug-15349-4717-sPBKSL64ic@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15349-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15349
--- Comment #2 from Raunaq M Bathija <raunaq at outlook dot com> 2013-04-19 06:58:36 UTC ---
(In reply to comment #1)
> (In reply to comment #0)
>
> > Is it very hard to get gcore working on AIX ?
>
> If you know the format of core files on AIX, then I think it
> shouldn't be too hard.
Ok, I know the format of core files on AIX. So basically, what that means is
that the AIX core file structure has a certain fields, I need to populate those
fields by gathering information (about the process being debugged) already
available to gdb and save it as a core file ?
If so, it would be really helpful if you could give me a an idea as to where in
gdb or which structure would save such information about the process being
debugged which would be helpful in filling the fields of the core structure.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-04-19 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 11:18 [Bug corefiles/15349] New: " raunaq at outlook dot com
2013-04-09 11:22 ` [Bug corefiles/15349] " raunaq at outlook dot com
2013-04-12 17:51 ` tromey at redhat dot com
2013-04-19 6:58 ` raunaq at outlook dot com [this message]
2014-03-12 10:02 ` palves at redhat dot com
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=bug-15349-4717-sPBKSL64ic@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).