Tom,
   Thanks for the reply. The button is on a picture module. I don't dynamically create the buttons, they are placed on 
the picture modules at design time in PhAB. I have several picture modules I am dynamically exchanging in and out of a 
pane on my base app window like this:

Button1Callback{
...
PtClearWidget(ABW_main_pane);
ApCreateModule(ABM_pic_module1 ,ABW_main_pane,NULL);
PtReRealizeWidget(ABW_main_pane);
...
}

Button2Callback{
..
PtClearWidget(ABW_main_pane);
ApCreateModule(ABM_pic_module2 ,ABW_main_pane,NULL);
PtReRealizeWidget(ABW_main_pane);
...
}
I changed the app to create all the picture modules at app startup on its own pane and now just move the panes in and 
out of the viewable area by changing X,Y coordinated and that has fixed the issue. But, is there some special 
characteristic of picture modules that could cause this SIGSEGV crash? I've done this dozens of times before with no 
such problems.
   Why would one button cause a SIGSEGV and another doing essentially the exact same thing not? 
  As far as a machine with QNX vs. VMWare...that makes no sense to me what so ever either!!!

Thanks again
John