| www.delorie.com/archives/browse.cgi | search |
On Jul 15 21:42, Dave Korn wrote: > Corinna Vinschen wrote: > > On Jul 15 20:32, Dave Korn wrote: > >> Yes. That's why I said "examine the SEH chain", not "look at the call > >> stack". I reckoned that doing so might provide any insight into why the > >> myfault was not invoked. For instance, you might see something hooked into > >> the SEH chain ahead of Cygwin's handler and start to look at what it was and > >> where it came from; and if not, you would be able to infer that the SEH chain > >> was not being invoked and start looking at the various SEH security > >> enhancements in recent windows versions and wondering which one might make it > >> think it shouldn't call handlers from a non-registered stack-based SEH > >> registration record. > > > > I'm not opposed to get some help with this stuff... > > I don't have 2k8 to test it on myself, but if you can get this reproducing > under the debugger, then use a command like > [...] Thanks for your help. I'm too tired right now to follow through. I'll look into it tomorrow. Thanks again, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |