From: Eli Zaretskii <eliz@gnu.org>
To: "André Pönitz" <apoenitz@t-online.de>
Cc: palves@redhat.com, brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [RFA 2/2][master only] gdb/windows-nat.c: Get rid of main_thread_id global
Date: Thu, 25 Apr 2019 05:39:00 -0000 [thread overview]
Message-ID: <83h8am1w5i.fsf@gnu.org> (raw)
In-Reply-To: <20190424201322.GB19677@klara.mpi.htwm.de> (message from =?iso-8859-1?Q?Andr=E9=09P=F6nitz?= on Wed, 24 Apr 2019 22:13:22 +0200)
> Date: Wed, 24 Apr 2019 22:13:22 +0200
> From: André Pönitz <apoenitz@t-online.de>
> Cc: palves@redhat.com, brobecker@adacore.com, gdb-patches@sourceware.org
>
> To be honest, I have still difficulties to find a mental model on what
> irks a typical Windows users. On one hand, they can apparently stand
> developing on that platform, on the other hand, two lines of extra
> output, even issued for consistency reasons, appear to be a show
> stopper.
That was sarcasm, I guess?
In any case, I'm not sure why you think developing for Windows in the
relevant use cases is something that needs some super-natural
endurance capabilities: I develop using Emacs, GCC, Binutils, GDB,
Grep, Find, and all the other tools you are familiar with. It's very
similar to developing on a Posix platform. GDB doesn't support debug
info in formats emitted by Windows compilers, it only supports
GCC-emitted info, AFAIK.
And two lines of extra output you don't expect are not a show-stopper,
but they do make you stop and think for a moment whether this is
something your code did.
next prev parent reply other threads:[~2019-04-25 5:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 22:33 Windows native GDB event handling enhancement Joel Brobecker
2019-04-16 22:33 ` [RFA 2/2][master only] gdb/windows-nat.c: Get rid of main_thread_id global Joel Brobecker
[not found] ` <83imvcg0ud.fsf@gnu.org>
2019-04-17 17:38 ` Joel Brobecker
2019-04-17 18:29 ` Eli Zaretskii
2019-04-17 22:17 ` Joel Brobecker
2019-04-18 12:52 ` Eli Zaretskii
2019-04-18 14:54 ` Joel Brobecker
2019-04-18 16:27 ` Pedro Alves
2019-04-19 20:43 ` Joel Brobecker
2019-04-22 14:24 ` Pedro Alves
2019-04-22 15:20 ` André Pönitz
2019-04-22 17:29 ` Pedro Alves
2019-04-22 21:42 ` André Pönitz
2019-04-23 5:54 ` Eli Zaretskii
2019-04-24 20:10 ` André Pönitz
2019-04-25 5:39 ` Eli Zaretskii [this message]
2019-04-23 11:42 ` Pedro Alves
2019-04-16 22:33 ` [RFA 1/2][master+8.3] (Windows) fix thr != nullptr assert failure in delete_thread_1 Joel Brobecker
2019-04-18 14:52 ` Pedro Alves
2019-04-18 15:04 ` Pedro Alves
2019-04-28 16:58 ` [v2] Windows native GDB event handling enhancement Joel Brobecker
2019-04-28 16:58 ` [RFA v2 2/2][master only] gdb/windows-nat.c: Get rid of main_thread_id global Joel Brobecker
2019-04-28 16:58 ` [RFA v2 1/2][master+8.3] (Windows) fix thr != nullptr assert failure in delete_thread_1 Joel Brobecker
2019-04-30 13:00 ` [v2] Windows native GDB event handling enhancement Pedro Alves
2019-04-30 21:04 ` pushed(master+8.3): " Joel Brobecker
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=83h8am1w5i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=apoenitz@t-online.de \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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