From: Pedro Alves <palves@redhat.com>
To: fracting@gmail.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 00/11] C++/MinGW patches
Date: Tue, 03 Nov 2015 16:54:00 -0000 [thread overview]
Message-ID: <5638E6C5.5040006@redhat.com> (raw)
In-Reply-To: <5638988C.5070601@redhat.com>
On 11/03/2015 11:20 AM, Pedro Alves wrote:
> On 11/03/2015 10:46 AM, Qian Hong wrote:
>> actual result:
>> gdb exit with error message: "This application has requested the
>> Runtime to terminate it in an unusual way. Please contact the
>> application's support team for more information." when debugging a
>> simple hello world program. "
>
> Hmm. Sounds like an uncaught C++ exception. I guess we could try
> making C++ mode use setjmp/longjmp exceptions like C mode, for confirmation.
>
>>
>> Then I tried build gdb again without build-with-cxx, and this error
>> disappear, gdb works as expect, at least for simple hello world.
I've pushed this patch:
https://sourceware.org/ml/gdb-patches/2015-11/msg00114.html
on the testing branch as well. I wonder if it makes a difference for you.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-11-03 16:54 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 19:36 Pedro Alves
2015-11-02 19:36 ` [PATCH 02/11] [C++/mingw] Misc alloca casts Pedro Alves
2015-11-02 19:36 ` [PATCH 04/11] [C++/mingw] windows-nat.c casts Pedro Alves
2015-11-02 19:36 ` [PATCH 01/11] [C++/mingw] ser-mingw.c casts Pedro Alves
2015-11-02 19:36 ` [PATCH 06/11] [C++/mingw] ser-tcp.c casts Pedro Alves
2015-11-02 20:40 ` Simon Marchi
2015-11-02 20:55 ` Pedro Alves
2015-11-02 21:06 ` Pedro Alves
2015-11-02 19:36 ` [PATCH 11/11] [C++/mingw] gdbserver: gdb/host signal mixup Pedro Alves
2015-11-02 19:36 ` [PATCH 10/11] [C++/mingw] Fix windows-nat.c::xlate Pedro Alves
2015-11-02 19:36 ` [PATCH 03/11] [C++/mingw] gdb-dlfcn.c casts Pedro Alves
2015-11-02 19:43 ` [PATCH 09/11] [C++/mingw] handle_output_debug_string Pedro Alves
2015-11-02 19:44 ` [PATCH 05/11] [C++/mingw] gdbserver casts Pedro Alves
2015-11-02 19:44 ` [PATCH 07/11] [C++/mingw] Define __STDC_CONSTANT_MACROS / __STDC_LIMIT_MACROS for stdint.h Pedro Alves
2015-11-02 20:47 ` Simon Marchi
2015-11-03 13:58 ` Simon Marchi
2015-11-03 14:07 ` Pedro Alves
2015-11-03 14:15 ` Simon Marchi
2015-11-03 15:13 ` Pedro Alves
2015-11-02 19:45 ` [PATCH 08/11] [C++/mingw] Simplify first chance exception handling Pedro Alves
2015-11-02 21:01 ` Simon Marchi
2015-11-02 21:09 ` Pedro Alves
2015-11-02 20:05 ` [PATCH 00/11] C++/MinGW patches Pedro Alves
2015-11-02 20:22 ` Qian Hong
2015-11-02 20:46 ` Pedro Alves
2015-11-02 21:17 ` Qian Hong
2015-11-02 23:31 ` Pedro Alves
2015-11-03 9:06 ` Qian Hong
2015-11-03 10:47 ` Qian Hong
2015-11-03 11:15 ` Qian Hong
2015-11-03 11:26 ` Pedro Alves
2015-11-03 11:41 ` Qian Hong
2015-11-03 12:11 ` Qian Hong
2015-11-03 12:34 ` Pedro Alves
2015-11-03 11:20 ` Pedro Alves
2015-11-03 16:54 ` Pedro Alves [this message]
2015-11-03 18:59 ` Qian Hong
2015-11-03 21:03 ` Qian Hong
2015-11-03 22:39 ` Pedro Alves
2015-11-09 9:53 ` Qian Hong
2015-11-17 14:50 ` Pedro Alves
2015-11-30 15:03 ` Qian Hong
2015-11-30 15:48 ` Pedro Alves
2015-11-03 12:24 ` Qian Hong
2015-11-03 12:27 ` Pedro Alves
2015-11-03 12:56 ` Qian Hong
2015-11-03 13:08 ` Pedro Alves
2015-11-03 13:23 ` Qian Hong
2015-11-03 16:52 ` Pedro Alves
2015-11-03 13:10 ` Pedro Alves
2015-11-02 21:04 ` Simon Marchi
2015-11-17 15:28 ` 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=5638E6C5.5040006@redhat.com \
--to=palves@redhat.com \
--cc=fracting@gmail.com \
--cc=gdb-patches@sourceware.org \
/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