From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Denis PILAT <denis.pilat@st.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] gdb is broken: missing signal.h checking
Date: Thu, 29 Mar 2007 17:48:00 -0000 [thread overview]
Message-ID: <20070329174808.GA28084@caradoc.them.org> (raw)
In-Reply-To: <19115.212.123.203.30.1175190093.squirrel@webmail.xs4all.nl>
On Thu, Mar 29, 2007 at 07:41:33PM +0200, Mark Kettenis wrote:
> > On my native linux gdb, I get "warning: Signal ? does not exist on this
> > system." when running.
> > It's just a missing line in the configure of gdb.
>
> signal.h is ISO C; we don't support systems that do not have it.
It turns out that this file is compiled for both GDB and gdbserver (a
long ago decision to try to reduce code duplication... I'm not
completely sure it was worth the hassle). GDB definitely does not
support systems without <signal.h>, but gdbserver now tries to. I
missed the problem when we just added WinCE support.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-29 17:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 15:07 Denis PILAT
2007-03-29 15:12 ` Daniel Jacobowitz
2007-03-29 15:25 ` Denis PILAT
2007-03-29 17:41 ` Mark Kettenis
2007-03-29 17:48 ` Daniel Jacobowitz [this message]
2007-03-30 12:01 ` Eli Zaretskii
2007-03-30 12:12 ` Daniel Jacobowitz
2007-03-30 12:23 ` Eli Zaretskii
2007-03-30 12:58 ` Daniel Jacobowitz
2007-03-30 12:23 ` Eli Zaretskii
2007-03-30 18:53 ` Mark Kettenis
2007-03-30 19:01 ` Daniel Jacobowitz
2007-03-30 21:04 ` Jim Blandy
2007-03-30 21:13 ` Daniel Jacobowitz
2007-03-29 20:37 ` 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=20070329174808.GA28084@caradoc.them.org \
--to=drow@false.org \
--cc=denis.pilat@st.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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