printing AND memory

[Ian Pilcher]

Richard Canada wrote:
> 
> After I ran wine under gdb, i did the "bt" and here is what I got:
> 
> 
> #0  0x40341f44 in __libc_read () from /lib/i686/libc.so.6
> #1  0x401053c4 in __DTOR_END__ () at eval.c:41
> #2  0x400d4c80 in WaitForMultipleObjectsEx (count=0, handles=0x0, 
> wait_all=0,
>      timeout=10, alertable=0) at synchro.c:348
> #3  0x400d4a28 in Sleep (timeout=10) at synchro.c:267
> #4  0x0107753d in ?? () at eval.c:41
    ...
> #62 0x0050c747 in ?? () at eval.c:41
> #63 0x00503fac in ?? () at eval.c:41
> #64 0x407b3b1b in WINPROC_wrapper () at winproc.c:119
> #65 0x407b3b8d in WINPROC_CallWndProc (proc=0x502a50, hwnd=2268, msg=1359,
>      wParam=0, lParam=0) at winproc.c:171
> #66 0x407b94bf in CallWindowProcA (func=0x40f80f60, hwnd=2268, msg=1359,
> #67 0x4079d26c in DispatchMessageA (msg=0x405f66d0) at message.c:925
> #68 0x005a1b79 in ?? () at eval.c:41
> #69 0x0040172c in ?? () at eval.c:41
> #70 0x00401d0a in ?? () at eval.c:41
> #71 0x400d17f4 in start_process () at process.c:390
> #72 0x400d4ee2 in SYSDEPS_DoCallOnStack (func=0x400d166c <start_process>,
>      arg=0x0) at sysdeps.c:173
> #73 0x400d4f83 in SYSDEPS_CallOnStack () at sysdeps.c:183
> #74 0x400d5029 in SYSDEPS_SwitchToThreadStack (func=0x400d166c 
> <start_process>)
>      at sysdeps.c:236
> #75 0x400d1b50 in PROCESS_InitWine (argc=3, argv=0xbffff96c,
>      win16_exe_name=0x804d5e0 "", win16_exe_file=0x804d6e4) at process.c:518
> #76 0x0804c160 in __do_global_ctors_aux () at main.c:84
> #77 0x40284177 in __libc_start_main (main=0x804c148 <main>, argc=3,
>      ubp_av=0xbffff96c, init=0x80486f8 <_init>, fini=0x804c1a0 <_fini>,
>      rtld_fini=0x4000e184 <_dl_fini>, stack_end=0xbffff95c)
>      at ../sysdeps/generic/libc-start.c:129
> 

The crash/exception isn't occuring in the PostScript driver, so I'm not
going to be able to add anything more.  Perhaps someone else will jump
in.

-- 
========================================================================
Ian Pilcher                                         ian.pilcher at home.com
========================================================================