[ros-dev] [ros-diffs] [hbelusca] 58135: [REACTOS] - Fix the debugging macros I've introduced in r58132; in particular do not use while(true); for forbidding the user to continue execution, but instead raise an exception...
For the kernel bugcheck I can emit, I've found another code:
FATAL_UNHANDLED_HARD_ERROR, what do you think about it ?
And for usermode, does it exist something else than abort() which doesn't
use the CRT, but which produces the same effects ? The exception will end up
in the exception handler usually, you say, but does it exist something else
that I can use (which can show up a msgbox to connect the debugger as
breakpoint or exception does BUT which stops the program exactly at the
point of the call) ?
-----Message d'origine-----
De : ros-dev-bounces at reactos.org [mailto:ros-dev-bounces at reactos.org] De la
part de Timo Kreuzer
Envoyé : lundi 7 janvier 2013 13:52
À : ReactOS Development List
Objet : Re: [ros-dev] [ros-diffs] [hbelusca] 58135: [REACTOS] - Fix the
debugging macros I've introduced in r58132; in particular do not use
while(true); for forbidding the user to continue execution, but instead
raise an exception...
We can use KeBugCheck / abort:
// for debug and release
#if kernelmode
#define FATAL() KeBugCheck(CRITICAL_SERVICE_FAILED) // <= didn't find a
better bugcheck code #else #define FATAL() abort(); #endif
or implement some Rtl function for that
#define UNIMPLEMENTED_FATAL() \
UNIMPLEMENTED;
ASSERT(FALSE);
FATAL()
Am 07.01.2013 01:55, schrieb Hermès BÉLUSCA - MAÏTO:
> Have you another solution in mind, to stop execution at this place BUT
> without being able to do 'cont' to continue the execution, when using
> the *_FATAL macros ? (the *_DBGBREAK macros should be fine, see my
> very last commit).
>> Hermès
>> -----Message d'origine-----
> De : ros-dev-bounces at reactos.org [mailto:ros-dev-bounces at reactos.org]
> De la part de Timo Kreuzer Envoyé : lundi 7 janvier 2013 01:14 À :
> ros-dev at reactos.org Objet : Re: [ros-dev] [ros-diffs] [hbelusca]
> 58135: [REACTOS] - Fix the debugging macros I've introduced in r58132;
> in particular do not use while(true); for forbidding the user to
> continue execution, but instead raise an exception...
>>> I see a problem with this change.
> A debug breakpoint will always break into the debugger exactly where it
is.
> Like an ASSERT does.
> But an exception will usually end up in the installed exception handler.
> This does not really help with figuring out what went wrong.
>> Am 07.01.2013 00:29, schrieb hbelusca at svn.reactos.org:
>> Author: hbelusca
>> Date: Sun Jan 6 23:29:05 2013
>> New Revision: 58135
>>>> URL: http://svn.reactos.org/svn/reactos?rev=58135&view=rev
>> Log:
>> [REACTOS]
>> - Fix the debugging macros I've introduced in r58132; in particular
>> do not
> use while(true); for forbidding the user to continue execution, but
> instead raise an exception with EXCEPTION_NONCONTINUABLE flag
> (included when called RtlRaiseStatus).
>> - Adjust the definition of RtlRaiseStatus (in kernel-mode it is
> ExRaiseStatus which is used).
>> Modified:
>> trunk/reactos/include/reactos/debug.h
>>>> Modified: trunk/reactos/include/reactos/debug.h
>> URL:
>> http://svn.reactos.org/svn/reactos/trunk/reactos/include/reactos/debu
>> g .h?rev=58135&r1=58134&r2=58135&view=diff
>> =====================================================================
>> =
>> ========
>> --- trunk/reactos/include/reactos/debug.h [iso-8859-1] (original)
>> +++ trunk/reactos/include/reactos/debug.h [iso-8859-1] Sun Jan 6
>> +++ 23:29:05 2013
>> @@ -15,7 +15,7 @@
>> #ifndef __INTERNAL_DEBUG
>> #define __INTERNAL_DEBUG
>>>> -/* Define DbgPrint/DbgPrintEx/RtlAssert unless the NDK is used */
>> +/* Define DbgPrint/DbgPrintEx/RtlAssert/RtlRaiseStatus unless the
>> +NDK is used */
>> #if !defined(_RTLFUNCS_H) && !defined(_NTDDK_)
>>>> /* Make sure we have basic types (some people include us *before*
>> SDK)... */ @@ -51,7 +51,27 @@
>> PCHAR Message
>> );
>>>> +#ifndef _NTDEF_ /* Guard against redefinition from ntdef.h */
>> + typedef _Return_type_success_(return >= 0) LONG NTSTATUS; #endif
>> +__analysis_noreturn NTSYSAPI VOID NTAPI RtlRaiseStatus(
>> + _In_ NTSTATUS Status
>> +);
>> +
>> #endif /* !defined(_RTLFUNCS_H) && !defined(_NTDDK_) */
>> +
>> +
>> +/* Fix usage of RtlRaiseStatus */
>> +#if !defined(_RTLFUNCS_H) && defined(_NTDDK_)
>> + #define RaiseStatus ExRaiseStatus #else
>> + #define RaiseStatus RtlRaiseStatus #endif /*
>> +!defined(_RTLFUNCS_H) && defined(_NTDDK_) */
>> +
>>>> #ifndef assert
>> #ifndef NASSERT
>> @@ -136,11 +156,7 @@
>>>> #endif /* not DBG */
>>>> -/*
>> - * These macros are designed to display an optional printf-like
>> - * user-defined message and to break into the debugger.
>> - * After that they allow to continue the program execution.
>> - */
>> +/*******************************************************************
>> +*
>> +**********/
>> /* For internal purposes only */
>> #define __ERROR_DBGBREAK(...) \
>> do { \
>> @@ -148,6 +164,18 @@
>> DbgBreakPoint(); \
>> } while (0)
>>>> +/* For internal purposes only */
>> +#define __ERROR_FATAL(Status, ...) \
>> +do { \
>> + DbgPrint("" __VA_ARGS__); \
>> + RaiseStatus((Status)); \
>> +} while (0)
>> +
>> +/*
>> + * These macros are designed to display an optional printf-like
>> + * user-defined message and to break into the debugger.
>> + * After that they allow to continue the program execution.
>> + */
>> #define ERROR_DBGBREAK(...) \
>> do { \
>> __NOTICE(ERROR, "\n"); \
>> @@ -165,19 +193,18 @@
>> * user-defined message and to break into the debugger.
>> * After that they halt the execution of the current thread.
>> */
>> -#define ERROR_FATAL(...) \
>> -do { \
>> - __NOTICE(UNRECOVERABLE ERROR, "\n"); \
>> - __ERROR_DBGBREAK(__VA_ARGS__); \
>> - while (TRUE); \
>> +#define ERROR_FATAL(...) \
>> +do { \
>> + __NOTICE(UNRECOVERABLE ERROR, "\n"); \
>> + __ERROR_FATAL(STATUS_ASSERTION_FAILURE, __VA_ARGS__); \
>> } while (0)
>>>> #define UNIMPLEMENTED_FATAL(...) \
>> do { \
>> __NOTICE(UNRECOVERABLE ERROR, "is UNIMPLEMENTED!\n"); \
>> - __ERROR_DBGBREAK(__VA_ARGS__); \
>> - while (TRUE); \
>> -} while (0)
>> + __ERROR_FATAL(STATUS_NOT_IMPLEMENTED, __VA_ARGS__); \
>> +} while (0)
>> +/*******************************************************************
>> +*
>> +**********/
>>>> #define ASSERT_IRQL_LESS_OR_EQUAL(x) ASSERT(KeGetCurrentIrql()<=(x))
>> #define ASSERT_IRQL_EQUAL(x) ASSERT(KeGetCurrentIrql()==(x))
>>>>>>>> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
_______________________________________________
Ros-dev mailing list
Ros-dev at reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
More information about the Ros-dev
mailing list
CHAPTER VII. THE FOUR CLASSES OF SOCIETY. THE FOUR CLASSES OF SOCIETY. "After the herald had given the names of the wrestlers who were to make the first round, the fellows came in. They were dressed without any clothes to speak of, or rather they were quite undressed, with the exception of a cloth around their loins. They came in on opposite sides of the ring, and stood there about five feet apart, each man resting his hands on his knees, and glaring at the other like a wild beast. They[Pg 231] looked more like a pair of tigers than human beings, and for a moment I thought it was not at all unlike what a bull-fight in Spain might be. I turned upon her choking with anger, but her melting beauty rendered me helpless. Black woods were on our left. "Shall we turn in here?" I asked. "None of that with me," he growled. "Do you know who I am, Countess Lalage? I am Leon Lagage, Count of the Holy Roman Empire, and your husband. Incomparable woman, you cannot alter that fact. For better or worse, for richer or poorer, till death do us part!" I have in this way imperfectly indicated a methodical plan of generating a design, as far as words alone will serve, beginning with certain premises based upon a particular work to be performed, and then proceeding to consider in consecutive order the general character of the machine, mode of operation, movements and adjustments, general arrangement, strains, special arrangement, and proportions. ‘Alas! what is life, what is death, what are we, 11th January two best dresses. Commencement was as usual, with a few showers “All right,” agreed Sandy. “Dick, you and I are the ground crew. As soon as you’re ready, Mr. Whiteside, we’ll take hold!” Effects of Walpole's Administration—Formation of the new Ministry—Attitude of the Malcontents—Committee of Inquiry into Walpole's Administration—Walpole's Protectors—Ministerial Measures—Prorogation of Parliament—Disasters of the French—British Division in the Netherlands—Opening of Parliament—The German Mercenaries—Amendment of the Gin Act—George goes to Germany—Stair and De Noailles in Franconia—Stair in a Trap—Bold Resolution of King George—The Battle of Dettingen—Resignation of Stair—Retreat of the French—Negotiations for Peace—Treaty of Worms—Pelham becomes Prime Minister—The Attacks of Pitt on Carteret—Attempted Invasion of England—Its Failure—Progress of the French Arms—Frederick II. invades Bohemia—His Retirement—Resignation of Carteret—Pelham strengthens his Ministry—Death of the Emperor—Campaign in Flanders—Battle of Fontenoy—Campaign of Frederick II.—The Young Pretender's Preparations—Loss of the Elizabeth—Landing in the Hebrides—The Highland Clans join him—The First Brush—Raising of the Standard—Cope's Mistake—He turns aside at Dalwhinnie—Charles makes a Dash for Edinburgh—The March to Stirling—Right of the Dragoons—The "Canter of Coltbridge"—Edinburgh surprised by the Highlanders—Charles marching against Cope—Battle of Prestonpans—Delay in marching South—Discontent of the Highland Chiefs—The Start—Preparations in England—Apathy of the Aristocracy—Arrival of the Duke of Cumberland—Charles crosses the Border—Capture of Carlisle—The March to Derby—Resolution to retreat—"Black Friday"—The Retreat—Recapture of Carlisle—Siege of Stirling—Battle of Falkirk—Retreat to the Highlands—Cumberland's Pursuit—Gradual Collapse of the Highlanders—Battle of Culloden—Termination of the Rebellion—Cruelty of the Duke of Cumberland—Adventures of the Young Pretender—Trials and Executions—Ministerial Crisis. The next morning he was up betimes, and cooked the boys as good a breakfast as he could out of the remainder of his store and what he could get from the hospital, and then gave what was left to whoever came. The comfortable crib, which had cost the Deacon so much labor, had been pre-empted by the Surgeon for some of his weakest patients. "You two step forward one pace," he commanded. "Gentleman, I've got my six. The rest are yours." "Where are you goin'?" he said sternly. Every now and then the crowd would break into the latest rhymings of MacKinnon's poet: A large thicket, at this moment, gave the dusty foot an opportunity of doubling, and, for an instant, diverging from the straightforward course, though it availed him little, he seemed to feel the breath of his pursuer on the back of his neck; his foot sounded as if at his heels; he drew his garment closely around him, turned suddenly to the right, and, bounding from the ground, the next instant a splash was heard in the little river, and the fugitive was safe from his pursuer. HoME明日之后怎么免费刷一级纳米材料
ENTER NUMBET 0018www.chattv.net.cn www.asdxjsc.com.cn bhggabc.com.cn www.chjld.com.cn www.618866.org.cn cqcq07.com.cn gbzb595.com.cn npzy.com.cn 400tour.com.cn www.huangzh.net.cn