I get this error when the debugger exists, and some breakpoints won't
work...
I'm also redirecting stdout in my program and writes to a file, but now
nothing gets written to disk. I was doing this before too, but then
everything worked, so I don't know if that could be the problem.

Ddbg 0.10 beta - D Debugger
see http://ddbg.mainia.de/doc.html for documentation

->Breakpoint set: C:\projects\in2dummy\trunk\src\i2f.d:772 0x404b48 all
->Expression evaluation depth is 1
->Starting debuggee in new console
Process terminated
->OUTPUT DEBUG STRING:
SXS: Unable to resolve storage root for assembly directory
x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03
in 2 tries

OUTPUT DEBUG STRING:
SXS: RtlGetAssemblyStorageRoot() unable to resolve storage map entry.
Status = 0xc0150004

Simen Haugen wrote:
> I get this error when the debugger exists, and some breakpoints won't
> work...

can you give me what i need to reproduce the breakpoints that don't work?

> I'm also redirecting stdout in my program and writes to a file, but now
> nothing gets written to disk. I was doing this before too, but then
> everything worked, so I don't know if that could be the problem.

it worked before what?

> Process terminated
> ->OUTPUT DEBUG STRING:
> SXS: Unable to resolve storage root for assembly directory
> x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03
> in 2 tries
>
> OUTPUT DEBUG STRING:
> SXS: RtlGetAssemblyStorageRoot() unable to resolve storage map entry.
> Status = 0xc0150004

these errors are output by the side-by-side assembly routines (SXS) via
the output debug string interface. that is, some DLL sends a string to
the debugger for display to the user (of the debugger). therefore they
are application errors. the fact that they appear after the process
termination has to be related to how these the win32 debugging
facilities cooperate with the SXS.

"Jascha Wetzel" <firstname@mainia.de> wrote in message
news:fego2f$1jov$1@digitalmars.com...
> Simen Haugen wrote:
>> I get this error when the debugger exists, and some breakpoints won't
>> work...
>
> can you give me what i need to reproduce the breakpoints that don't work?

>> I'm also redirecting stdout in my program and writes to a file, but now
>> nothing gets written to disk. I was doing this before too, but then
>> everything worked, so I don't know if that could be the problem.
>
> it worked before what?

Thats what I don't know. The project is in the start phase, and I haven't
added it to version control yet...

>> Process terminated
>> ->OUTPUT DEBUG STRING:
>> SXS: Unable to resolve storage root for assembly directory
>> x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03
>> in 2 tries
>>
>> OUTPUT DEBUG STRING:
>> SXS: RtlGetAssemblyStorageRoot() unable to resolve storage map entry.
>> Status = 0xc0150004
>
> these errors are output by the side-by-side assembly routines (SXS) via
> the output debug string interface. that is, some DLL sends a string to the
> debugger for display to the user (of the debugger). therefore they are
> application errors. the fact that they appear after the process
> termination has to be related to how these the win32 debugging facilities
> cooperate with the SXS.


Open the Run Dialog and create a new Environment Variable "SystemPath" with value
"C:\Windows"  or, if you did not install windows to the default directory then
wherever it is installed.

I mailed Jascha the code, and I think he has a fix for it already.
Looking forward to 0.11

"Nicki Newby" <newby@niancrae.com> wrote in message
news:ff39eo$2n9j$1@digitalmars.com...
> Open the Run Dialog and create a new Environment Variable "SystemPath"
> with value
> "C:\Windows"  or, if you did not install windows to the default directory
> then
> wherever it is installed.

If you or Jascha have a different fix, I'd appreciate hearing what it is.  I had to search on  non-D programming forums to figure this out.  It seems that the compiler is looking for comctl32.dll in the referenced directory.  There should be other ways of setting the SystemPath.  But this fix is easy and works.

Simen Haugen Wrote:

> I mailed Jascha the code, and I think he has a fix for it already.
> Looking forward to 0.11
>

Nicki Newby wrote:
> If you or Jascha have a different fix, I'd appreciate hearing what it is.  I had to search on  non-D programming forums to figure this out.  It seems that the compiler is looking for comctl32.dll in the referenced directory.  There should be other ways of setting the SystemPath.  But this fix is easy and works.
>
> Simen Haugen Wrote:
>
>> I mailed Jascha the code, and I think he has a fix for it already.
>> Looking forward to 0.11

i think you are talking about two different issues.
my fix will be for the incorrect breakpoints, not the SXS issue.