Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@gnu.org>
To: cagney@gnu.org
Cc: eliz@gnu.org, joseph@codesourcery.com, kevinb@redhat.com,
	gdb-patches@sources.redhat.com
Subject: Re: Assume solib.h
Date: Tue, 16 Nov 2004 19:18:00 -0000	[thread overview]
Message-ID: <200411161917.iAGJHqO8000702@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <419A2742.8070804@gnu.org> (message from Andrew Cagney on Tue, 16 Nov 2004 11:13:54 -0500)

   Date: Tue, 16 Nov 2004 11:13:54 -0500
   From: Andrew Cagney <cagney@gnu.org>

   >>and how my change breaks it?
   > 
   > 
   > This part I don't know the details about.  Mark said that it does
   > break, and I spoke on the assumption that you agree with the fact of
   > breakage,

   Unfortunatly your assumption is wrong.  As I stated to Mark, and 
   contrary to his assertion, powerpc-elf passes this sniff test:

   $ gcc -g -static src/gdb/testsuite/gdb.base/break{,1}.c
   cagney@to-dhcp51$ ./X-powerpc-elf/gdb/gdb ./a.out
   warning: A handler for the OS ABI "GNU/Linux" is not built into this 
   configuration
   of GDB.  Attempting to continue with the default powerpc:common settings.
   (gdb) target sim
   Connected to the simulator.
   (gdb) load
   (gdb) run
   Starting program: /home/scratch/PENDING/YYYY-MM-DD-solib/a.out
   do_call() unimplemented call settimeofday
   (gdb) disassemble
   No frame selected.
   <oops>
   (gdb) x/i $pc
   0x10008a10 <uname+4>:   sc

Yup, I'm wrong.  Not *every* embedded target will break.  Some of them
include solib-svr4.o or some other solib-xxx.o; powerpc-elf is one of
them.  I'm also wrong that it breaks vax-dec-openbsd* for pretty much
the same reason.  However, there are plenty of embedded targets for
which I'm pretty certain that my analysis is true: arm-elf, mips-elf,
i386-elf are among them.

Mark


  reply	other threads:[~2004-11-16 19:18 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 19:39 Andrew Cagney
2004-11-11 20:06 ` Mark Kettenis
2004-11-11 21:48   ` Andrew Cagney
2004-11-11 22:24     ` Mark Kettenis
2004-11-12 15:52       ` Andrew Cagney
2004-11-12 17:20         ` Eli Zaretskii
2004-11-15 21:32           ` Kevin Buettner
2004-11-15 23:35             ` Mark Kettenis
2004-11-17 17:35             ` Eli Zaretskii
2004-11-15 23:59           ` Andrew Cagney
2004-11-16  1:20             ` Daniel Jacobowitz
2004-11-16  5:00             ` Eli Zaretskii
2004-11-16  8:37               ` Mark Kettenis
2004-11-16 20:54                 ` Eli Zaretskii
2004-11-16 16:14               ` Andrew Cagney
2004-11-16 19:18                 ` Mark Kettenis [this message]
2004-11-18 14:10                   ` Andrew Cagney
2004-11-18 14:37                     ` Mark Kettenis
2004-11-18 17:28                       ` Kevin Buettner
2004-11-19 17:11                       ` Andrew Cagney
2004-11-19 17:25                         ` Randolph Chung
2004-11-19 17:36                           ` Joel Brobecker
2004-11-19 17:40                             ` Randolph Chung
2004-11-19 17:56                               ` Joel Brobecker
2004-11-19 19:29                         ` Joseph S. Myers
2004-11-16 21:06                 ` Eli Zaretskii
2004-11-16 22:27                   ` Andrew Cagney
2004-11-17  4:52                     ` Eli Zaretskii
2004-11-16  1:40         ` Daniel Jacobowitz
2004-11-16  4:54           ` Eli Zaretskii
2004-11-16 16:31           ` Andrew Cagney
2004-11-16 19:45             ` Mark Kettenis
2004-11-16 21:06             ` Eli Zaretskii
2004-11-12  1:11 ` Randolph Chung
2004-11-13  1:10   ` Andrew Cagney

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=200411161917.iAGJHqO8000702@elgar.sibelius.xs4all.nl \
    --to=kettenis@gnu.org \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=kevinb@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