Date: Sat, 5 Jun 2004 00:04:20 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 393 ************************************************** Friday 04 June 2004 Number 393 ************************************************** Subjects for today 1 _asm {int 3} : Dave Webster 2 RE: _asm {int 3} : Dave Webster 3 RE: _asm {int 3} : Dave Webster 4 pthreads : Dave Webster 5 RE: [wx-discuss] pthreads : Dave Webster 6 Re: _asm {int 3} : Stefan.Neis at t-online.de **= Email 1 ==========================** Date: Thu, 3 Jun 2004 08:52:09 -0500 From: Dave Webster Subject: _asm {int 3} This inline assembler call will invoke the configured debugger on Windows (Borland C++, Visual C++, etc..) and OS/2 (IPMD). The debugger comes up and then loads the application at the point of the call. Will this work for gdb on Linux (or a gdb-like debugger on other Intel platforms)?? **= Email 2 ==========================** Date: Thu, 3 Jun 2004 09:12:59 -0500 From: Dave Webster Subject: RE: _asm {int 3} On a related note, how, exactly, does one call interrupts under gcc. Can't seem to figure out what gcc wants for syntax. Using __asm__ ( "int 3" ) yields an assembler error: suffix or operands invalid....? -----Original Message----- From: Dave Webster [mailto:Dave.Webster at bhmi.com] Sent: Thursday, June 03, 2004 8:52 AM To: Unix-OS2 (E-mail 2) Subject: _asm {int 3} This inline assembler call will invoke the configured debugger on Windows (Borland C++, Visual C++, etc..) and OS/2 (IPMD). The debugger comes up and then loads the application at the point of the call. Will this work for gdb on Linux (or a gdb-like debugger on other Intel platforms)?? **= Email 3 ==========================** Date: Thu, 3 Jun 2004 09:37:42 -0500 From: Dave Webster Subject: RE: _asm {int 3} OK, it is asm("whatever"). To call a X86 debug instruction under gcc it would be asm("int3") or __asm__ ("int $3") -----Original Message----- From: Dave Webster [mailto:Dave.Webster at bhmi.com] Sent: Thursday, June 03, 2004 9:13 AM To: 'os2-unix at mail.warpix.org' Subject: RE: _asm {int 3} On a related note, how, exactly, does one call interrupts under gcc. Can't seem to figure out what gcc wants for syntax. Using __asm__ ( "int 3" ) yields an assembler error: suffix or operands invalid....? -----Original Message----- From: Dave Webster [mailto:Dave.Webster at bhmi.com] Sent: Thursday, June 03, 2004 8:52 AM To: Unix-OS2 (E-mail 2) Subject: _asm {int 3} This inline assembler call will invoke the configured debugger on Windows (Borland C++, Visual C++, etc..) and OS/2 (IPMD). The debugger comes up and then loads the application at the point of the call. Will this work for gdb on Linux (or a gdb-like debugger on other Intel platforms)?? **= Email 4 ==========================** Date: Thu, 3 Jun 2004 13:22:25 -0500 From: Dave Webster Subject: pthreads Anyone have a good online reference to the POSIX pthread library? **= Email 5 ==========================** Date: Thu, 3 Jun 2004 13:24:15 -0500 From: Dave Webster Subject: RE: [wx-discuss] pthreads Nevermind. Found a good one at http://www.llnl.gov/computing/tutorials/workshops/workshop/pthreads/MAIN.htm l -----Original Message----- From: Dave Webster [mailto:Dave.Webster at bhmi.com] Sent: Thursday, June 03, 2004 1:22 PM To: WxDiscuss (E-mail); Unix-OS2 (E-mail 2) Subject: [wx-discuss] pthreads Anyone have a good online reference to the POSIX pthread library? --------------------------------------------------------------------- To unsubscribe, e-mail: wx-discuss-unsubscribe at lists.wxwidgets.org For additional commands, e-mail: wx-discuss-help at lists.wxwidgets.org **= Email 6 ==========================** Date: Fri, 4 Jun 2004 10:44:42 +0100 From: Stefan.Neis at t-online.de Subject: Re: _asm {int 3} Hi, > This inline assembler call will invoke the configured debugger on Windows > (Borland C++, Visual C++, etc..) and OS/2 (IPMD). The debugger comes up and > then loads the application at the point of the call. Will this work for gdb > on Linux (or a gdb-like debugger on other Intel platforms)?? No idea. Normally, I just load the executable into the debugger ("gdb samples.exe") set the breakpoint, I want (e.g. "break sample.c:53" to set a breakpoint in line 53 of file sample.c or "break functionname" to break as soon as function "functionname" is entered) and "run" the program. HTH, Stefan