From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sources.redhat.com
Subject: Re: Broken cast in linux-thread-db
Date: Wed, 12 Oct 2005 14:33:00 -0000 [thread overview]
Message-ID: <jey84yst3c.fsf@sykes.suse.de> (raw)
In-Reply-To: <20051012142427.GA21308@nevyn.them.org> (Daniel Jacobowitz's message of "Wed, 12 Oct 2005 10:24:27 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> I think the current behavior is actually more correct despite any
> warning.
GCC _always_ sign extends, which is definitely wrong here.
> Were you fixing an observed problem?
If notify.u.bptaddr has the high bit set it will be sign extended, but the
breakpoint address when the thread event breakpoint is hit will be zero
extended, so they don't match and the breakpoint is not recognized.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-10-12 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 14:13 Andreas Schwab
2005-10-12 14:24 ` Daniel Jacobowitz
2005-10-12 14:33 ` Andreas Schwab [this message]
2005-10-12 14:41 ` Daniel Jacobowitz
2005-10-12 15:59 ` Andreas Schwab
2005-10-12 17:43 ` 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=jey84yst3c.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@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