running gdb in cygwin

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

running gdb in cygwin

Krisakorn Rerkrai
Hi,

I have a problem with running gdb in the cygwin.
I searched in the archive and found some descriptions
but not really solve my problem.

This is my result:

(gdb) run 2
Starting program: /opt/tinyos- 1.x/apps/Oscilloscope/build/pc/main.exe 2
SIM: Random seed is 828125
1: LEDS: Yellow off.
1: LEDS: Red off.
1: LEDS: Green off.

Program received signal SIGSEGV, Segmentation fault.
0x7c809f62 in KERNEL32!IsBadWritePtr ()
   from /cygdrive/c/WINDOWS/system32/kernel32.dll
(gdb)

One solution refers to
http://www.cygwin.com/ml/cygwin/2004-04/msg00569.html
I have tried to "continue" the process. I have to type "continue"
at least 3 times each time it is stuck with this fault. This is
quite annoying. Is there any other clean solution for this?

Thank you in advance.
Krisakorn


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Reply | Threaded
Open this post in threaded view
|

Re: running gdb in cygwin

Christopher Faylor-2
On Wed, Jan 04, 2006 at 02:21:33PM +0100, Krisakorn Rerkrai wrote:

>I have a problem with running gdb in the cygwin.
>I searched in the archive and found some descriptions
>but not really solve my problem.
>
>This is my result:
>
>(gdb) run 2
>Starting program: /opt/tinyos- 1.x/apps/Oscilloscope/build/pc/main.exe 2
>SIM: Random seed is 828125
>1: LEDS: Yellow off.
>1: LEDS: Red off.
>1: LEDS: Green off.
>
>Program received signal SIGSEGV, Segmentation fault.
>0x7c809f62 in KERNEL32!IsBadWritePtr ()
>   from /cygdrive/c/WINDOWS/system32/kernel32.dll
>(gdb)
>
>One solution refers to
>http://www.cygwin.com/ml/cygwin/2004-04/msg00569.html
>I have tried to "continue" the process. I have to type "continue"
>at least 3 times each time it is stuck with this fault. This is
>quite annoying. Is there any other clean solution for this?

Since cygwin no longer uses "IsBadWritePtr", it sounds like you are
using an older DLL version.  Using the guidelines mentioned at
http://cygwin.com/problems.html would allow us to know this for sure.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/