From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Put a NT_PSTATUS note on solaris cores.
Date: Sun, 11 Oct 2009 21:21:00 -0000 [thread overview]
Message-ID: <8ac60eac0910111421p6afbfbe9ha4544bddc75943ab@mail.gmail.com> (raw)
In-Reply-To: <200910090236.10584.pedro@codesourcery.com>
On Thu, Oct 8, 2009 at 6:36 PM, Pedro Alves <pedro@codesourcery.com> wrote:
> 2009-10-09 Pedro Alves <pedro@codesourcery.com>
>
> gdb/
> * procfs.c (procfs_make_note_section): Always output a NT_PSTATUS
> note when NEW_PROC_API is defined.
This causes build failure on 32-bit solaris-10:
gcc -g -O2 \
-o gdb gdb.o libgdb.a \
../readline/libreadline.a ../opcodes/libopcodes.a
../bfd/libbfd.a ./../intl/libintl.a ../libiberty/libiberty.a
../libdecnumber/libdecnumber.a -ldl -lcurses -lz -lsocket -lnsl -lm
-lpython2.4 -lexpat ../libiberty/libiberty.a gnulib/libgnu.a
Undefined first referenced
symbol in file
elfcore_write_pstatus libgdb.a(procfs.o)
ld: fatal: Symbol referencing errors. No output written to gdb
collect2: ld returned 1 exit status
bfd/elf.c defines elfcore_write_pstatus only when HAVE_PSTATUS_T
From bfd/config.log:
configure:14057: checking for pstatus_t in sys/procfs.h
configure:14075: gcc -c -g -O2 conftest.c >&5
conftest.c: In function `main':
conftest.c:81: error: `pstatus_t' undeclared (first use in this function)
This appears to be a bfd configury bug: AFAIC, pstatus_t is defined if
'#include <procfs.h>, but not if '#include <sys/procfs.h>', because
the former defines _STRUCTURED_PROC to 1, and the latter to 0.
Not sure what the proper fix is.
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-10-11 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 1:36 Pedro Alves
2009-10-11 21:21 ` Paul Pluzhnikov [this message]
2009-10-11 22:10 ` Pedro Alves
2009-10-11 22:35 ` Paul Pluzhnikov
2009-10-11 22:40 ` Pedro Alves
2009-10-11 23:21 ` Paul Pluzhnikov
2009-10-31 16:34 ` Paul Pluzhnikov
2009-10-31 21:00 ` Pedro Alves
2009-10-31 23:26 ` Paul Pluzhnikov
2009-10-11 22:53 ` Pedro Alves
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=8ac60eac0910111421p6afbfbe9ha4544bddc75943ab@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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