This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug win32/14529] New: Make gdb capable of JIT-debugging on W32


http://sourceware.org/bugzilla/show_bug.cgi?id=14529

             Bug #: 14529
           Summary: Make gdb capable of JIT-debugging on W32
           Product: gdb
           Version: 7.5
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: win32
        AssignedTo: unassigned@sourceware.org
        ReportedBy: lrn1986@gmail.com
    Classification: Unclassified


Created attachment 6618
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6618
Adds --event=EVENT commandline argument for attaching to a crashing process on
W32

To be a JIT-debugger [1] on Windows, gdb has to be able to signal an event,
which is passed to it by command line. If that is not done, the process being
debugged will not come out of a waiting loop after gdb attaches to it.
If the event is signaled, Windows will break the loop, and let the exception
fall into gdb's lap (well, stack will be a bit borked, but that's another issue
for another day, and there are ways of working around it), after gdb user does
'continue'.

The attached patch does exactly that by adding extra "--event=EVENT" argument,
thus AeDebug command line will look like this:
c:\mingw32\bin\gdb.exe --pid=%ld --event=%ld

[1] http://msdn.microsoft.com/en-us/library/5hs4b7a6%28v=vs.80%29.aspx

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]