Bug Vanquisher

13 July 2008

Someone Please Fix ASLR!

Filed under: Windows Vista — Tanveer Badar @ 4:45 PM

Not the feature but what it means. I have heard/read over 3 different expansions for the abbreviation.

ASLR: Address space layout randomization.
ASLR: Address space load randomization.

And some more which I forgot. Its just a mass confusion over what the term actually means while the implementation is simple to explain.

One boot, you get dlls loaded like A B C D E F
Second boot, you get dlls loaded like D E C B A F

And that’s it.

3 May 2008

Previous Versions

Filed under: Windows Vista — Tanveer Badar @ 10:17 PM

They don’t exist in Windows Vista Enterprise Edition, or do they? For me they do and this is how.

Woes and Worries

Filed under: Bugz, Rant vs Vent, Windows Vista — Tanveer Badar @ 5:52 PM

I wonder why people cry of the sucky video drivers pushed out by NVidia. The monsters Intel rolls out for their D946 GZ chipsets must be on par. I have had more GPU resets from them than power failures!

Even new yahoo messenger causes the graphics stack to crash weirdly.

[Update-After five minutes]

Here’s the most charming, updated EULA of the driver I downloaded.

This file should be replaced by the current license file when built.

 

I mean what they are playing at?

8 March 2008

Why The Hell Are You Still Here!

Filed under: Rant vs Vent, Windows Vista — Tanveer Badar @ 7:22 PM

Configuring Updates: Stage 3 of 3 – 100% Complete

Uninstalling Service Pack: Stage 2 of 3 – 100% Complete

Uninstalling Service Pack: Stage 3 of 3 – 100% Complete

Everything 100% complete, yet still on computer screen!

17 January 2008

Screw Up. Fixed!

Filed under: Windows Vista — Tanveer Badar @ 11:12 PM

Finally, my Windows Vista installation is up and running again. Only two or three programs of my usual set remain to be installed.

Why the reinstall? Well, I managed to install SP1 RC refresh last week and it didn’t work anymore.

7 January 2008

After the Service Pack

Filed under: Debugging, Windows Vista — Tanveer Badar @ 11:46 PM

A nice analysis you get after you install Windows Vista SP1. The reason, no debugging symbols available as of right now.

The problem was caused by visiting this page in IE7. FF 3 beta 2 seems to work fine (at least it does not crash each and every time). So, if anyone can help, you are welcome.


0:000> !analyze
*******************************************************************************
*                        Exception Analysis                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ieui.dll, ieframe.dll, iexplore.exe, kernel32.dll –
***** OS symbols are WRONG. Please fix symbols to do analysis.

************************************************************************************
***    Your debugger is not using the correct symbols                         ***
***    In order for this command to work properly, your symbol path    ***
***    must point to .pdb files that have full type information.            ***
***    Certain .pdb files (such as the public OS symbols) do not           ***
***    contain the required information.  Contact the group that          ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                                                      ***
***    Type referenced: ntdll!_PEB                                                      ***
*************************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ole32.dll –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for rpcrt4.dll –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for msvcrt.dll –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for msidcrl40.dll –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for pdm.dll –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for mshtml.dll –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for winmm.dll –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for wdmaud.drv –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for mswsock.dll –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ws2_32.dll –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for wininet.dll –
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for jscript.dll –

************************************************************************************
***    Your debugger is not using the correct symbols                         ***
***    In order for this command to work properly, your symbol path    ***
***    must point to .pdb files that have full type information.            ***
***    Certain .pdb files (such as the public OS symbols) do not           ***
***    contain the required information.  Contact the group that          ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                                                      ***
***    Type referenced: ntdll!_PEB                                                      ***
*************************************************************************************

************************************************************************************
***    Your debugger is not using the correct symbols                         ***
***    In order for this command to work properly, your symbol path    ***
***    must point to .pdb files that have full type information.            ***
***    Certain .pdb files (such as the public OS symbols) do not           ***
***    contain the required information.  Contact the group that          ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                                                      ***
***    Type referenced: kernel32!pNlsUserInfo                                     ***
*************************************************************************************

************************************************************************************
***    Your debugger is not using the correct symbols                         ***
***    In order for this command to work properly, your symbol path    ***
***    must point to .pdb files that have full type information.            ***
***    Certain .pdb files (such as the public OS symbols) do not           ***
***    contain the required information.  Contact the group that          ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                                                      ***
***    Type referenced: kernel32!pNlsUserInfo                                     ***
*************************************************************************************

************************************************************************************
***    Your debugger is not using the correct symbols                         ***
***    In order for this command to work properly, your symbol path    ***
***    must point to .pdb files that have full type information.            ***
***    Certain .pdb files (such as the public OS symbols) do not           ***
***    contain the required information.  Contact the group that          ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                                                      ***
***    Type referenced: kernel32!pNlsUserInfo                                     ***
*************************************************************************************
Probably caused by : ieui.dll ( ieui!DUserRegisterSuper+a79 )

Followup: MachineOwner
———


Oh and I almost forgot, the stack trace.


WARNING: Stack unwind information not available. Following frames may be wrong.
001fe630 7777ff75 001fe5e4 001fe658 00000000 ntdll!KiFastSystemCallRet
001fe684 73486071 00000030 001fe6b8 ffffffff user32!GetWindowRect+0x16c
001fe6a4 73486353 000004ff ffffffff 00000000 ieui!DUserRegisterSuper+0xa79
001fe6cc 734862f9 000004ff 00000000 6f1137ba ieui!WaitMessageEx+0x8b
001fe708 6f0af412 003a1788 001fe738 6f09305b ieui!WaitMessageEx+0x31
001fe714 6f09305b 00000000 00000000 00353df0 ieframe!Ordinal101+0x1a727
001fe738 6f095b28 1c70000a 00353df0 00000000 ieframe!Ordinal160+0x1281
001ff7a8 6f094e2a 00353df0 00000001 77055f59 ieframe!Ordinal101+0xe3d
001ff9d8 01333036 00322490 0000000a 01340070 ieframe!Ordinal101+0x13f
001ffe1c 01332eca 01330000 00000000 00321a00 iexplore+0x3036
001ffeb0 77181cc2 7ffdc000 001ffefc 77b087d5 iexplore+0x2eca
001ffebc 77b087d5 7ffdc000 77efc35d 00000000 kernel32!BaseThreadInitThunk+0x12
001ffefc 77b087a8 01332d4d 7ffdc000 00000000 ntdll!RtlInitializeExceptionChain+0x64
001fff14 00000000 01332d4d 7ffdc000 00000000 ntdll!RtlInitializeExceptionChain+0x37

25 December 2007

The Bug in the Bug

Filed under: Bugz, Rant vs Vent, Windows Vista — Tanveer Badar @ 9:20 PM

Yesterday, I installed Windows Vista SP1 on my box. Everything works fine, except three!

Network icon is very shy of showing the actual connectivity of my computer on the internet. It takes two minutes to update from clip_image001 to clip_image001[5]. Not remotely amusing. Thank God, I have my modem sitting right in front of me to have a look at those five LEDs. Such a time saver.

It is possible to boot the system from cold faster than it is able to resume from sleep from cold. The wonders of sleep optimizations.

And this leads to the last issue. It is not possible to submit this report to Microsoft, because the tool included in SP1 is for beta releases of Windows Vista. It fails to update itself, always downloads a copy of the program when run again, saves reports in a format it cannot itself read, is never able to establish a connection to Microsoft servers for report submission, the error it shows in this case redirects to a page which keeps refreshing itself without ever showing anything, shows Longhorn in its UI instead of Vista.

8 December 2007

Real News

Filed under: Fun, Windows Vista — Tanveer Badar @ 4:02 PM

image

Guess what! I kept wondering why Windows XP suddenly started displaying all windows with AERO borders. :)

16 November 2007

I Demand An Explanation

Filed under: Funnier, Rant vs Vent, Windows Vista — Tanveer Badar @ 2:26 AM

image

They say “A picture is worth a thousand words”. Therefore, I’ll keep this post very short and let you figure out and tell me which part of hardware is from ATI/AMD on my system when everything screams an “Intel Inside”!

Perhaps, these may help you make your decision quickly.

image
(from msinfo32)

image
(from device manager)

Is Microsoft playing “Idiot Outside”? Do count this when making announcing the verdict.

11 October 2007

Definitely Buggy

Filed under: Bugz, Windows Vista — Tanveer Badar @ 7:48 PM

Windows Update is definitely buggy, no matter what Microsoft says otherwise.

I must lay the foundations before beginning the story. I never let Windows Update get away with silently installing the update offered. For Windows XP, I always go to %windir%\softwaredistribution\download folder and copy the installation files to a separate directory. This copying means I never have to download that same update again unless it is re-offered.

For Windows Vista, the process is slightly easy as so far I have not been able to find the location or commandline of installation process which is always run by TrustedInsaller program. Therefore, I follow the help link given in details of each individual update and download the microsoft update standalone package from knowledge base or technet and never have to download it again.

That’s where “The cumulative security update for Internet Explorer 7 in Windows Vista (KB939653)” comes into the picture. The information link given in the details for this update is

More information:
http://go.microsoft.com/fwlink/?LinkId= 95045

which means there are two problems, first note the white space after ‘=’ and five digit incorrect KB code. Following the usual steps I noticed that this update was never found in KB. Therefore, I had to google for KB939653 for a working link to knowledge base article.

Older Posts »

Blog at WordPress.com.