#534 closed defect (fixed)
Trap in Stubby on startup
Reported by: | Gregg Young | Owned by: | Gregg Young |
---|---|---|---|
Priority: | minor | Milestone: | Release_3.24 |
Component: | fm/2 base | Version: | 3.21 |
Keywords: | Cc: |
Description (last modified by )
Fix was not adequate needed (INT) pci != -1 check
Attachments (1)
Change History (9)
by , 11 years ago
Attachment: | 012E_0C.TRP added |
---|
comment:1 by , 11 years ago
comment:2 by , 10 years ago
Milestone: | Release_3.23 → Release_3.24 |
---|
Ticket retargeted after milestone closed
comment:3 by , 9 years ago
Milestone: | Release_3.24 → Release_3.25 |
---|
comment:4 by , 9 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:5 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:6 by , 9 years ago
Description: | modified (diff) |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
comment:8 by , 9 years ago
Milestone: | Release_3.25 → Release_3.24 |
---|
Note:
See TracTickets
for help on using tickets.
The second check is where the trap occurred:
there are some clues. It almost seems like pciParent was not yet fully initialized when the trap occurred. By our rules, under normal conditions, pszFileName is never NULL.
EDX points to pciParent, so we can look at its contents. At the time the ..trp file was written [edx+0x20] contains a valid pointer. You may have an SMP timing race.
I have a full trap dump pdump.292