From: todd.kallam@acterna.com
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB bug: target.c (target_signal_from_host): unrecognized real -time signal on arm
Date: Tue, 25 Jun 2002 07:55:00 -0000 [thread overview]
Message-ID: <85256BE3.0051C5EF.00@wg.com> (raw)
Hi,
I have had the same problem with each of the following versions:
insight+dejagnu-5.2.0_20020624.tar.bz2
gdb+dejagnu-weekly-CVS-5.2.0_20020618.tar.bz2
gdb-5.2.tar.gz
I configure gdb with the following command:
./configure --target=arm-linux
I configured gdbserver with the following command:
./configure arm-linux
The following insight+dejagnu-5.2.0_20020624.tar.bz2 code in
gdb/signals/signals.c reports the problem:
#if defined (SIGRTMIN)
if (hostsig >= SIGRTMIN && hostsig <= SIGRTMAX)
{
/* This block of TARGET_SIGNAL_REALTIME value is in order. */
if (33 <= hostsig && hostsig <= 63)
return (enum target_signal)
(hostsig - 33 + (int) TARGET_SIGNAL_REALTIME_33);
else if (hostsig == 64)
return TARGET_SIGNAL_REALTIME_64;
else
error ("GDB bug: target.c (target_signal_from_host): unrecognized real-time
signal");
}
#endif
Regards,
Todd
Daniel Jacobowitz <drow@mvista.com> on 06/24/2002 06:04:58 PM
To: Todd Kallam/Engineering/TTC/US@Global
cc: gdb@sources.redhat.com
Subject: Re: GDB bug: target.c (target_signal_from_host): unrecognized real
-time signal on arm
I committed a fix for this problem at the same time I committed the
multithread support. Could you be more specific about which snapshot
you are using?
On Mon, Jun 24, 2002 at 05:33:44PM -0400, todd.kallam@acterna.com wrote:
>
>
>
> Hi,
>
> I am trying to use the latest snapshot of gdb to do remote debugging
> of a multithreaded Qt application on a strongarm processor running
> linux. I get the following message shown by gdbserver on the target:
>
> GDB bug: target.c (target_signal_from_host): unrecognized real-time signal
>
> The hostsig value is 32, but this value is not handled by the code.
>
> Has any one else had this problem?
>
> I am using gcc 2.95.3 for arm-linux and kernel version 2.4.18 with arm
patches.
> Thanks for any help.
>
> Regards,
>
> Todd
>
>
>
>
>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-06-25 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 7:55 todd.kallam [this message]
2002-06-25 8:03 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-06-25 11:11 todd.kallam
2002-06-24 14:36 todd.kallam
2002-06-24 15:05 ` Daniel Jacobowitz
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=85256BE3.0051C5EF.00@wg.com \
--to=todd.kallam@acterna.com \
--cc=drow@mvista.com \
--cc=gdb@sources.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