Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Dave Murphy <wintermute2k4@ntlworld.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch] Build arm-elf-gdb on mingw host
Date: Mon, 26 Sep 2005 03:59:00 -0000	[thread overview]
Message-ID: <20050926035937.GA24565@nevyn.them.org> (raw)
In-Reply-To: <uslvsjxtp.fsf@gnu.org>

On Mon, Sep 26, 2005 at 06:46:10AM +0300, Eli Zaretskii wrote:
> > Date: Mon, 26 Sep 2005 00:23:39 +0100
> > From: Dave Murphy <wintermute2k4@ntlworld.com>
> > 
> > When building the bfd/doc directory under mingw/msys chew.c converts 
> > line endings to crlf.  I've patched so the files are read as binary, 
> > preventing this conversion.
> 
> Why?  What's wrong with having the output from chew have CRLF line
> endings on Windows?

Yeah, I'm wondering about this too.

> > SIGTRAP isn't defined in the MinGW headers, I patched remote-sim.c to 
> > define this if it's not defined.
> 
> I don't think this is a good idea.  It is much better (and widely
> practiced) to #ifdef away portions of code that use SIGTRAP, like
> this:
> 
>     #ifdef SIGTRAP
>     ... code that depends on SIGTRAP ...
>     #endif

In this case, unfortunately, it's a bit more complicated to fix.  You
can find a similar workaround patch from Paul Brook in the archives,
and my discussion (with Mark?) about it.  The gdb<->sim interface uses
"signals", meaning the host signal numbers.  And without SIGTRAP we
can't step or breakpoint.  Thus, a lot of files in sim already define
SIGTRAP.

They ought to be converted to the relatively new "gdb/signals.h" header
in include/, but the simulators are also concerned with actual host
signals in places, so a simple search and replace isn't right either.
It's going to take a little investigation to fix this properly.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-09-26  3:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-25 23:23 Dave Murphy
2005-09-26  3:46 ` Eli Zaretskii
2005-09-26  3:59   ` Daniel Jacobowitz [this message]
2005-09-26  4:46     ` Dave Murphy
2005-09-26 13:23       ` Daniel Jacobowitz
2005-09-26 14:09         ` Christopher Faylor
2005-09-26 14:14           ` Daniel Jacobowitz
2005-09-26 14:26             ` Christopher Faylor
2005-09-26 14:31               ` Daniel Jacobowitz
2005-09-26 15:41                 ` Christopher Faylor
2005-09-26 19:18                 ` Eli Zaretskii
2006-04-08 20:21               ` Daniel Jacobowitz
2006-04-10 16:51                 ` Christopher Faylor
2006-04-10 16:58                   ` Daniel Jacobowitz
2005-09-26 19:16             ` Eli Zaretskii
2005-09-27  2:02               ` Christopher Faylor
2005-09-26 19:13           ` Eli Zaretskii
2005-09-26 19:08       ` Eli Zaretskii

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=20050926035937.GA24565@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=wintermute2k4@ntlworld.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