{"id":107469,"date":"2022-11-28T07:00:01","date_gmt":"2022-11-28T15:00:01","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/oldnewthing\/?p=107469"},"modified":"2022-11-26T08:21:06","modified_gmt":"2022-11-26T16:21:06","slug":"20221128-01","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20221128-01\/?p=107469","title":{"rendered":"What kind of caller diagnostic information can I get from exceptions thrown by C++\/WinRT and wil?, C++20 edition"},"content":{"rendered":"

A short time ago, I summarized the kind of caller diagnostic information you can get from exceptions thrown by C++\/WinRT and wil<\/a>. My colleague David Machaj<\/a> reminded me that the story had improved in the time since I originally wrote the article, so it’s time for an update.<\/p>\n

Starting in version 2.0.220929.3 of C++\/WinRT, if std::source_location<\/code> is supported, then C++\/WinRT uses it to pass file and line number information to wil<\/a> when a C++\/WinRT exception is thrown. In practice, this happens when you compile in C++20 mode or later.<\/p>\n

The revised table now looks like this:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
\u00a0<\/th>\nC++\/WinRT<\/th>\nwil<\/th>\n<\/tr>\n
no wil\/cppwinrt.h<\/code><\/th>\nwith wil\/cppwinrt.h<\/code><\/th>\nno C++\/CX<\/th>\nwith C++\/CX<\/th>\n<\/tr>\n
throw hresult_error<\/code><\/th>\ncheck_hresult<\/code><\/th>\nTHROW_IF_FAILED<\/code><\/th>\nTHROW_IF_FAILED<\/code><\/th>\n<\/tr>\n
Thrown type<\/td>\nhresult_error<\/code><\/td>\nhresult_error<\/code><\/td>\nhresult_error<\/code><\/td>\nResult\u00adException<\/code><\/td>\nException^<\/code><\/td>\n<\/tr>\n
Stack trace in thrown object<\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nYes<\/td>\n<\/tr>\n
Stack trace in thread data<\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nRequires result_originate.h<\/code><\/td>\nYes<\/td>\n<\/tr>\n
File\/line number in thrown object<\/td>\nNo<\/td>\nNo<\/td>\nNo<\/td>\nYes<\/td>\nNo<\/td>\n<\/tr>\n
Exception in wil error log<\/td>\nNo<\/td>\nNo<\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\n<\/tr>\n
File\/line number in wil error log<\/td>\nNo<\/td>\nRequires C++20<\/td>\nRequires C++20<\/td>\nYes<\/td>\nYes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

The state of the art has moved forward slightly.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[25],"class_list":["post-107469","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"

The state of the art has moved forward slightly.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/107469","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=107469"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/107469\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=107469"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=107469"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=107469"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}