Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Harald Koenig <H.Koenig@science-computing.de>,
	 Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org,  Harald Koenig <koenig@science-computing.de>
Subject: Build errors on AIX
Date: Wed, 24 Feb 2010 13:35:00 -0000	[thread overview]
Message-ID: <201002241335.07011.pedro@codesourcery.com> (raw)
In-Reply-To: <20100224125136.GA14069@atuin.science-computing.de>

[removing bug-gdb@]

On Wednesday 24 February 2010 12:51:36, Harald Koenig wrote:
> On Feb 23, Harald Koenig wrote:
> 
> > right now I'm trying to build gdb on AIX 6.1 which right now fails here
> > 
> >       "gdb-CVS-20100222/gdb/aix-thread.c", line 352.46: 1506-280 (W) Function argument assignment between types "int*" and "unsigned int*" is not allowed.
                                                    ^^^^^^

How does one read that?  line 352, column 46?  On my sources,
352 has:

352:	  if (!ptrace32 (PTT_READ_GPRS, tid, gprs32, 0, NULL))
353:	    memset (gprs32, 0, sizeof (gprs32));

> > where the source reads like this -- hmmmmm....
> > 
> >   /* getthrds(3) isn't prototyped in any AIX 4.3.3 #include file.  */
> >   extern int getthrds (pid_t, struct thrdsinfo64 *,
> >                        int, pthdb_tid_t *, int);
> 

Anyway, ignoring line numbers, what's the compiler complaining about?
Is it the signness of pthdb_tid_t that is wrong?

> with the attached patch AIX 6.1 builds fine, and 5.1 still does so....
> (_AIX51 is defined in 5.2/5.3 too!  I've not tested 5.0 though which is 
> why I don't check _AIX50 which is defined in 5.1-5.3 too).

It would perhaps be better to autoconf the getthrds declaration being
present, here, in gdb/configure.ac:

   aix*)
      AC_MSG_CHECKING(for AiX thread debugging library)
      AC_CACHE_VAL(gdb_cv_have_aix_thread_debug,
                   [AC_TRY_COMPILE([#include <sys/pthdebug.h>],
                                   [#ifndef PTHDB_VERSION_3
                                    #error
                                    #endif],
                                   gdb_cv_have_aix_thread_debug=yes,
                                   gdb_cv_have_aix_thread_debug=no)])
      AC_MSG_RESULT($gdb_cv_have_aix_thread_debug)
      if test $gdb_cv_have_aix_thread_debug = yes; then
         CONFIG_SRCS="${CONFIG_SRCS} aix-thread.c"
         CONFIG_OBS="${CONFIG_OBS} aix-thread.o"
         CONFIG_LDFLAGS="${CONFIG_LDFLAGS} -lpthdebug"
      fi
      ;;
   esac

But I really don't know much about AIX.  Joel?  What do you
think?  You seem to be one of that last that touched
this `getthrds' bit of code.  :-)

> but:  6.1 has the same break point problems as 5.3:
> 
> - with no breakpoint before 1st run, break points can't be set later at all
> 
> - otherwise break points seem to work

I can't really guess exactly what's going on here.  AIX/RS6000
is probably the port that most needs love of all the supported
ports.  E.g, I wouldn't be surprised if recent changes like PIE
or multi-program support and the revamping around these broke
this port, for it does things in non-standard ways.  These
commands may offer some clues:

 "(gdb) maint info breakpoints"
 "(gdb) set debug infrun 1"
 "(gdb) set target infrun 1"

If you have an older gdb that works, I think we get to
debug the new gdb to try to track this down.

-- 
Pedro Alves


  reply	other threads:[~2010-02-24 13:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100215141621.GA9469@atuin.science-computing.de>
2010-02-18 19:23 ` some compile errors fo gdb-7.0.1 Pedro Alves
2010-02-23 15:22   ` Harald Koenig
2010-02-23 17:08     ` Pedro Alves
2010-02-23 16:35   ` Harald Koenig
2010-02-23 17:14     ` Harald Koenig
2010-02-24 12:51       ` Harald Koenig
2010-02-24 13:35         ` Pedro Alves [this message]
2010-02-24 14:09           ` Build errors on AIX Harald Koenig
2010-03-01  6:47           ` Joel Brobecker
2010-03-01  6:51     ` some compile errors fo gdb-7.0.1 Joel Brobecker

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=201002241335.07011.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=H.Koenig@science-computing.de \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=koenig@science-computing.de \
    /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