From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Pedro Alves'" <pedro_alves@portugalmail.pt>,
<gdb-patches@sourceware.org>
Subject: RE: Fix annoying misleading pointer
Date: Thu, 25 Oct 2007 12:09:00 -0000 [thread overview]
Message-ID: <003201c816de$c8fa5960$5aef0c20$@u-strasbg.fr> (raw)
In-Reply-To: <4053daab0710241538q64e3db8et926d111d8b086ada@mail.gmail.com>
Too bad I didn't read that earlier,
I just spent a l..ong time trying to
find where those TARGET_SIGNAL definitions
really were!
Thanks for correcting this!
Pierre
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Pedro Alves
> Sent: Thursday, October 25, 2007 12:39 AM
> To: gdb-patches@sourceware.org
> Subject: Fix annoying misleading pointer
>
> Hi,
>
> Was looking at Mach exceptions, and was bitten by this once again.
> Hopefully this will be the last.
>
> Tested by following the directions with emacs.
>
> Cheers,
> Pedro Alves
prev parent reply other threads:[~2007-10-25 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 0:39 Pedro Alves
2007-10-25 6:02 ` Joel Brobecker
2007-10-25 21:47 ` Pedro Alves
2007-10-25 12:09 ` Pierre Muller [this message]
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='003201c816de$c8fa5960$5aef0c20$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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