User forums > Nightly builds

The 18 June 2006 build is out.

<< < (6/12) > >>

thomas:

--- Quote from: Pecan on June 19, 2006, 06:30:42 pm ---Is there a possibility that this behavior is caused by the SIGTRAP's that are buried in ntdll.dll?
--- End quote ---
Who could tell what is possible... :)  I don't believe so, though.

The exceptions that are caught (according to MSDN) are:
EXCEPTION_ACCESS_VIOLATION
EXCEPTION_ARRAY_BOUNDS_EXCEEDED
EXCEPTION_BREAKPOINT
EXCEPTION_DATATYPE_MISALIGNMENT
EXCEPTION_FLT_DENORMAL_OPERAND
EXCEPTION_FLT_DIVIDE_BY_ZERO
EXCEPTION_FLT_INEXACT_RESULT
EXCEPTION_FLT_INVALID_OPERATION
EXCEPTION_FLT_OVERFLOW
EXCEPTION_FLT_STACK_CHECK
EXCEPTION_FLT_UNDERFLOW
EXCEPTION_ILLEGAL_INSTRUCTION
EXCEPTION_IN_PAGE_ERROR
EXCEPTION_INT_DIVIDE_BY_ZERO
EXCEPTION_INT_OVERFLOW
EXCEPTION_INVALID_DISPOSITION
EXCEPTION_NONCONTINUABLE_EXCEPTION
EXCEPTION_PRIV_INSTRUCTION
EXCEPTION_SINGLE_STEP
EXCEPTION_STACK_OVERFLOW

It does not say anything about traps caused by file I/O or anything. If it were related to I/O then we should have seen that crash before, shouldn't we. Remember that I have been using the crash handler 10-12 hours daily for 46 days 66 days without ever seeing such a thing (and a few other people have used it for the same time).

royalbox:
@Pecan
I downloaded and installed gdb-5.2.1-1.exe. This is the output I get after typing 'run':


--- Code: ---Starting program: C:\Program Files\Code Blocks\codeblocks.exe
---Type <return> to continue, or q <return> to quit---

Program received signal SIGSEGV, Segmentation fault.
0x77ea3c00 in _libkernel32_a_iname ()
(gdb)

--- End code ---
code::blocks doesn't get past the splash screen.
I tried this on the last nightly that works on my system just to test. Am I doing something wrong?

EDIT:
This was the output before typing 'run':

--- Code: ---This GDB was configured as "i686-pc-mingw32"...(no debugging symbols found)...

--- End code ---

Do I need a debug version of the nightly? I'm not up on debugging yet, I keep putting it off.

Michael:

--- Quote from: royalbox on June 19, 2006, 08:55:34 pm ---@Pecan
I downloaded and installed gdb-5.2.1-1.exe. This is the output I get after typing 'run':

--- End quote ---

Hello,

You should download gdb 6.3.x. gdb 5.2.x does not work (pending breakpoints).

Best wishes,
Michael

Pecan:

--- Quote from: royalbox on June 19, 2006, 08:55:34 pm ---@Pecan
I downloaded and installed gdb-5.2.1-1.exe. This is the output I get after typing 'run':


--- Code: ---Starting program: C:\Program Files\Code Blocks\codeblocks.exe
---Type <return> to continue, or q <return> to quit---

Program received signal SIGSEGV, Segmentation fault.
0x77ea3c00 in _libkernel32_a_iname ()
(gdb)

--- End code ---

--- End quote ---

Are you running under cygwin or some other non-windows shell?

You must have downloaded the wrong gdb. It should be gdb 6.3 for windows.

Look here: http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks
It has a link to download MinGW for MS Windows.

pecan

Pecan:

--- Quote from: Pecan on June 19, 2006, 06:40:22 pm ---
These sigtraps happend after I installed MSVC on my laptop about a year ago. My old system, which has never had MSVC on it, does *not* get these sigtraps when running GDB.


--- End quote ---

@royalbox, et.al. with crash

For the machine that gets these crashes; have you ever installed Microsoft debugger, Visual Studio, .Net, or any of the MS compiler/debugger toolkits?

thanks
pecan

Navigation

[0] Message Index

[#] Next page

[*] Previous page