Bugs item #1686497, was opened at 2007-03-22 23:25
Message generated for change (Comment added) made by datallah
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100235&aid=1686497&group_id=235
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: win32
Group: 2.0.0 beta 6
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Brant Gurganus (brantgurga)
Assigned to: Daniel Atallah (datallah)
Summary: First chance access violation for current stack trace.
Initial Comment:
GTK+ 2.10.11
Glib 2.12.11
Gaim 2.00beta6
1. Run Application Verifier (free from Microsoft).
2. Add Gaim.exe.
3. Press Save. (some of the basic checks should be enabled by default).
4. Start gaim.
Gaim will crash at startup and looking at the Application Verifier log, the
cause was a first chance access violation for current stack trace. Log with
stack trace follows. The help file gives the following information about this
verification:
Application Verifier break message
First chance access violation for current stack trace.
Probable cause
This is the most common application verifier stop. Typically it is caused by a
buffer overrun error. The heap verifier places a non-accessible page at the end
of a heap allocation and a buffer overrun will cause an exception by touching
this page. There are several other causes for this stop. For example, accessing
a heap block after being freed. The same debugger command will be useful for
this case too.
Information displayed by Application Verifier
Parameter1 - Invalid address causing the exception
Parameter2 - Code address executing the invalid access
Parameter3 - Exception record. Context Record
Parameter4 - Context record
Description - First chance access violation for current stack trace
Additional information
Verifier Stop code 0013.
To debug this stop identify the access address that caused the exception and
then use the following debugger command:
!heap -p -a ACCESS_ADDRESS This command will give details about the nature of
the error and what heap block is overrun. It will also give the stack trace for
the block allocation.
Copyright © 2006 by Microsoft Corporation. All rights reserved.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<avrf:logfile xmlns:avrf="Application Verifier">
<avrf:logSession TimeStarted="2007-03-23 : 00:07:21" PID="3096"
Version="2">
<avrf:logEntry Time="2007-03-23 : 00:07:30" LayerName="Heaps"
StopCode="0x13" Severity="Error">
<avrf:message>First chance access violation for current
stack trace.</avrf:message>
<avrf:parameter1>7dc4fac - Invalid address causing the
exception.</avrf:parameter1>
<avrf:parameter2>70525c52 - Code address executing the
invalid access.</avrf:parameter2>
<avrf:parameter3>8f7f858 - Exception
record.</avrf:parameter3>
<avrf:parameter4>8f7f8a8 - Context
record.</avrf:parameter4>
<avrf:stackTrace>
<avrf:trace>vrfcore!VfCoreRedirectedStopMessage+81</avrf:trace>
<avrf:trace>vfbasics!VfBasicsStopMessage+1c9</avrf:trace>
<avrf:trace>vfbasics!AVrfpCheckFirstChanceException+139</avrf:trace>
<avrf:trace>vfbasics!AVrfpVectoredExceptionHandler+18</avrf:trace>
<avrf:trace>ntdll!RtlInitializeCriticalSectionAndSpinCount+93f</avrf:trace>
<avrf:trace>ntdll!RtlCaptureContext+10f</avrf:trace>
<avrf:trace>ntdll!RtlUnwind+15c</avrf:trace>
<avrf:trace>ntdll!KiUserExceptionDispatcher+f</avrf:trace>
<avrf:trace>vfbasics!AVrfpRtlLeaveCriticalSection+6c</avrf:trace>
<avrf:trace>libgaim!gaim_whiteboard_set_brush+31a</avrf:trace>
<avrf:trace>msvcrt!atof_l+447</avrf:trace>
<avrf:trace>msvcrt!beginthreadex+c9</avrf:trace>
<avrf:trace>vfbasics!AVrfpStandardThreadFunction+6f</avrf:trace>
<avrf:trace>kernel32!BaseThreadInitThunk+e</avrf:trace>
<avrf:trace>ntdll!RtlCreateUserProcess+8c</avrf:trace>
</avrf:stackTrace>
</avrf:logEntry>
</avrf:logSession>
</avrf:logfile>
----------------------------------------------------------------------
>Comment By: Daniel Atallah (datallah)
Date: 2007-04-01 01:08
Message:
Logged In: YES
user_id=325843
Originator: NO
The stacktrace doesn't appear to be accurate (I've seen that pretty
frequently when using windbg with files containing debug symbols in a
non-native format), however I was able to get a better backtrace using the
mingw gdb. I'm testing a fix, if it works out, I'll include it in the next
release.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100235&aid=1686497&group_id=235
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Gaim-bugs mailing list
Gaim-bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gaim-bugs
