RtlUnicodeStringToAnsiString failed

NTDEV
1

Hi,

I’m analysing a crash dump where the function didn’t return STATUS_SUCCESS:

RtlUnicodeStringToAnsiString(&componentName, &unicodeString, TRUE);

The immediate reason for a crash was using NULL componentName.Buffer.

I want to know what can be the reason that RtlUnicodeStringToAnsiString
fails. I ran !pcr to see irql=0, checked contents of unicodeString (12
us-ascii wide characters at 00143bbe), !memusage shown plenty of memory. OS:
W2k sp3.

Any ideas?

2

If you mean that RtlUnicodeStringToAnsiString didn’t return STATUS_SUCCESS,
then you have violated one of the NTDEV Cluestick Rules: if you are asking
for help about a DDK API failure you must document the actual NTSTATUS
returned by the API if you expect to get actual informed answers.

There are several reasons besides memory allocation errors that can cause
this api to fail.

=====================
Mark Roddy
Hollis Technology Solutions
www.hollistech.com
xxxxx@hollistech.com

-----Original Message-----
From: Joze Fabcic [mailto:xxxxx@hermes.si]
Sent: Tuesday, July 01, 2003 8:16 AM
To: NT Developers Interest List
Subject: [ntdev] RtlUnicodeStringToAnsiString failed

Hi,

I’m analysing a crash dump where the function didn’t return STATUS_SUCCESS:

RtlUnicodeStringToAnsiString(&componentName, &unicodeString, TRUE);

The immediate reason for a crash was using NULL componentName.Buffer.

I want to know what can be the reason that RtlUnicodeStringToAnsiString
fails. I ran !pcr to see irql=0, checked contents of unicodeString (12
us-ascii wide characters at 00143bbe), !memusage shown plenty of memory. OS:
W2k sp3.

Any ideas?

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

3

If the life would be that simple. I inherited the source code that didn’t
store the result of RtlUnicodeStringToAnsiString. Everything I know is that
the componentName.Buffer was zero and from documentation I deduced that the
function didn’t return STATUS_SUCCESS. Can you list some of “several
reasons”?

Thanks in advance
Joze

-----Original Message-----
From: Roddy, Mark [mailto:xxxxx@stratus.com]

If you mean that RtlUnicodeStringToAnsiString didn’t return STATUS_SUCCESS,
then you have violated one of the NTDEV Cluestick Rules: if you are asking
for help about a DDK API failure you must document the actual NTSTATUS
returned by the API if you expect to get actual informed answers.

There are several reasons besides memory allocation errors that can cause
this api to fail.

=====================
Mark Roddy
Hollis Technology Solutions
www.hollistech.com
xxxxx@hollistech.com

-----Original Message-----
From: Joze Fabcic [mailto:xxxxx@hermes.si]
Sent: Tuesday, July 01, 2003 8:16 AM
To: NT Developers Interest List
Subject: [ntdev] RtlUnicodeStringToAnsiString failed

Hi,

I’m analysing a crash dump where the function didn’t return STATUS_SUCCESS:

RtlUnicodeStringToAnsiString(&componentName, &unicodeString, TRUE);

The immediate reason for a crash was using NULL componentName.Buffer.

I want to know what can be the reason that RtlUnicodeStringToAnsiString
fails. I ran !pcr to see irql=0, checked contents of unicodeString (12
us-ascii wide characters at 00143bbe), !memusage shown plenty of memory. OS:
W2k sp3.

Any ideas?

You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@hermes.si
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

Are you able to debug the code? If so, you can see the result in the EAX
register after the call. It needn’t be stored in a variable in order to
be observed.

Chuck

----- Original Message -----
From: “Joze Fabcic”
To: “NT Developers Interest List”
Sent: Tuesday, July 01, 2003 9:13 PM
Subject: [ntdev] RE: RtlUnicodeStringToAnsiString failed

> If the life would be that simple. I inherited the source code that
didn’t
> store the result of RtlUnicodeStringToAnsiString. Everything I know is
that
> the componentName.Buffer was zero and from documentation I deduced
that the
> function didn’t return STATUS_SUCCESS. Can you list some of “several
> reasons”?
>
> Thanks in advance
> Joze