hi!
one more guess:
the reported error originates from opening "vos/utile/defs/wntmsci<whatever>". looking at the code, a reason for failure might be a unusual setting of the environment variable "COMP_ENV" (or simply a "disk full" ;-)).
tschau...
ause
Richard Gadsden wrote:
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Hans-Joachim Lankenau) wrote:
hi!
"cvs checkout" should have created a directory "vos/util/defs". that's where this tool (ldump) wants to write its output. if this directory doesn't exist or isn't writeable, you'll get this error.
"$SRC_ROOT/vos/util/defs" is there and has a bunch of files in called things like "wntmsci9". Having checked, it's definitely writeable to the user I'm running as (me).
I'm getting an exception in ldump4.exe. After lots of digging, Visual Studio reports it as "Unhandled exception at 0x7c901010 in ldump4.exe: 0xC0000005: Access violation reading location 0x00000034.
I can give you a disassembly of the bit of ldump4.exe where it errored, but I think that's probably useless information - if you really want it, then I'll give you the appropriate bit.
Windows XP's error reporting has buried some data on this with Microsoft. I believe there is a way for Sun (as authors of ldump4.exe) to get hold of this if they really want to, but I doubt it's very useful.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
