Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: RFA: probable rs6000-aix-tdep.c bug found by clang
Date: Thu, 18 Oct 2012 09:10:00 -0000	[thread overview]
Message-ID: <507FC786.50400@redhat.com> (raw)
In-Reply-To: <20121017212417.GP3050@adacore.com>

On 10/17/2012 10:24 PM, Joel Brobecker wrote:
> 
>> Based on indentation and logic I think that the fix is to remove the ";".
>> However, I have no decent way to test this and would appreciate someone
>> else looking at it.
> [...]
>> 2012-10-17  Tom Tromey  <tromey@redhat.com>
>>
>> 	* rs6000-aix-tdep.c (rs6000_aix_osabi_sniffer): Remove extraneous
>> 	semicolon.

I suspect this is the root cause of PR8966 (AIX 5.1 single_step configuration
is broken).  http://sourceware.org/bugzilla/show_bug.cgi?id=8966

We're always returning the _UNKNOWN osabi, so this is unreachable:

static void
rs6000_aix_init_osabi (struct gdbarch_info info, struct gdbarch *gdbarch)
{
  struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch);

  /* RS6000/AIX does not support PT_STEP.  Has to be simulated.  */
  set_gdbarch_software_single_step (gdbarch, rs6000_software_single_step);
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> In fact, going one step further, do we need the check at all?
> This is how the sniffer is registered:
> 
>   gdbarch_register_osabi_sniffer (bfd_arch_rs6000,
>                                   bfd_target_xcoff_flavour,
>                                   rs6000_aix_osabi_sniffer);
>   gdbarch_register_osabi_sniffer (bfd_arch_powerpc,
>                                   bfd_target_xcoff_flavour,
>                                   rs6000_aix_osabi_sniffer);
> 
> So, isn't rs6000_aix_osabi_sniffer going to be called if, and only
> if, the bfd has a bfd_target_xcoff_flavour, thus making the check
> superfluous?

Sure looks like it.

-- 
Pedro Alves


  reply	other threads:[~2012-10-18  9:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 20:06 Tom Tromey
2012-10-17 21:24 ` Joel Brobecker
2012-10-18  9:10   ` Pedro Alves [this message]
2012-10-18 15:33     ` Joel Brobecker
2012-10-18 15:46       ` Pedro Alves
2012-10-18 15:58         ` Joel Brobecker
2012-10-18 16:06           ` Pedro Alves
2012-10-18 18:49       ` Joel Brobecker
2012-10-18 19:43         ` Tom Tromey
2012-10-19 20:00         ` 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=507FC786.50400@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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