public inbox for
 help / color / mirror / Atom feed
From: Simon Marchi <>
To: Claude Robitaille <>,
	"" <>
Subject: Re: GDB is preventing my catch blocks in my C++ program
Date: Tue, 12 Apr 2022 21:33:38 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Claude,

Please make sure to do a reply all so everyone on the list can see your
reply and contribute.

On 2022-04-12 21:28, Claude Robitaille wrote:
> Thanks Simon for the quick reply.
> I can single step the program up to the point where an exception is thrown. And I did set a breakpoint inside the catch statement but no success (earlier breakpoint in the code are working as expected).
> Here is what appears on the console (yes, it is Windows)
> Listening on port 2345
> Remote debugging from host, port 34542
> Error while doing a GetTokenInformation - Unknown errorLOGGER NOT INITIALIZED:
>                 *********************************************************************************************
> terminate called after throwing an instance of 'sf::context::tGlobal::envVariableMissing'
> Child exited with status 3

> The string that starts with Error blah blah is my own std::cout earlier in the program. Same with the line with the ******
> and the LOGGER xxxx is from the g3log library in my program.
> The exception instance is definitely what my program is throwing.

Indeed, that makes it clear it's not gdbserver crashing.

I don't have any idea at the moment about how gdb/gdbserver could affect
the execution of your program in this way.

> I guess Child exited is from gdb.



  parent reply	other threads:[~2022-04-13  1:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  0:27 Claude Robitaille
2022-04-13  1:17 ` Simon Marchi
     [not found]   ` <>
2022-04-13  1:33     ` Simon Marchi [this message]
2022-04-13  1:39     ` Claude Robitaille
2022-04-14 15:06       ` Claude Robitaille
2022-04-15 15:55         ` Claude Robitaille
2022-04-18  0:45           ` Simon Marchi

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).