topic Re: wxWidgets-2.6.2 symbolic stack dump in Operating System - OpenVMS

wxWidgets-2.6.2 symbolic stack dump

CoreDump — Fri, 16 Feb 2007 13:16:24 GMT

Hello All,

I am new to OpenVMS however I have working with Alpha for number of years.

Anyway I am trying to build wxWidgets-2.6.2 on OpenVMS 8.2 with Motif and version 6.4 C++ of the compiler.

I can get wxWidgets-2.6.2 and the dialogs to build however when I go run the sample I get the following core dump any ideas why?

X Toolkit Warning: Cannot convert string "-*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000004, PC=FFFFFFFF80E93E74, PS=0000001B %TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
DECW$XTLIBSHRR5 0 0000000000057E74
FFFFFFFF80E93E74
dialogs utils wxDoChangeBackgroundColour
69011 000000000000309C 000000000038E10C
dialogs menu SetBackgroundColour 66957 0000000000003448
0000000000201608
dialogs menu SetBackgroundColour 66970 0000000000003484
0000000000201644
dialogs menu CreateMenu 66877 000000000000314C
000000000020130C
dialogs menu CreateMenuBar 66729 00000000000029AC
0000000000200B6C
dialogs dialogs OnInit 63782 0000000000007D48
00000000001E7D48
dialogs dialogs CallOnInit 40296 00000000000012A8
00000000001E12A8
dialogs init wxEntry 41061 00000000000011F4
000000000041DBB4
dialogs dialogs main 63509 0000000000003F54
00000000001E3F54
dialogs dialogs __MAIN 0 0000000000000070
00000000001E0070
dialogs 0 00000000004C41C8
00000000004C41C8
PTHREAD$RTL 0 00000000000572E8
FFFFFFFF80A512E8
PTHREAD$RTL 0 0000000000030444
FFFFFFFF80A2A444
0 FFFFFFFF80333F94
FFFFFFFF80333F94

Re: wxWidgets-2.6.2 symbolic stack dump

Hoff — Fri, 16 Feb 2007 13:38:42 GMT

Hello and welcome to ITRC.

One of the most powerful tools around these parts is the OpenVMS debugger.

Recompile your source code port with /DEBUG/NOOPTIMIZE on all of your source modules and then LINK your resulting image(s) with /DEBUG, then re-invoke your application. You'll end up in the OpenVMS debugger, and you can then step forward to the particular trigger for this access violation (ACCVIO) error.

The access violation produces details of the specific error; see HELP/MESSAGE ACCVIO. The cryptic values displayed will tell what was happening when the error occured -- a read or write, and to what virtual address, and from what instruction. In this case, it looks to be something inside the x library that blew up, which generally points to an argument-passing or related error.

I'd look at the handling within the code around the font conversion, as I could easily see an unhandled or mishandled error case causing problems later in the code; a snow-balling error.

Using STEP commands and other such, the debugger will allow you to walk forward through the code, and determine what might be happening.

There's a potentially interesting discussion on wxWidgets here:
http://nchrem.tnw.tudelft.nl/openvms/software2.html
and which discusses a compilation fix.

Stephen Hoffman
HoffmanLabs

Re: wxWidgets-2.6.2 symbolic stack dump

Jansen_8 — Tue, 20 Feb 2007 06:35:02 GMT

Note :
1) wxMOTIF is not the best maintained version of wxWidgets (not only on OpenVMS)
2) 2.8.x is now the current version
3) The best version for VMS is currently wxGTK with gtk1.x

Jouk