Re: gdb hangs on ^Z [was: Re: 64-bit gdb: invalid decimal " 0x22DBF0"]

On 29/07/2013 3:27 PM, Ryan Johnson wrote: On 29/07/2013 3:13 PM, Ryan Johnson wrote: On 29/07/2013 3:11 PM, Corinna Vinschen wrote: On Jul 29 12:01, Ryan Johnson wrote: On 29/07/2013 7:06 AM, Corinna Vinschen wrote: On Jul 27 11:30, Daniel Brown wrote: I have also ran into this problem, in

Re: gdb hangs on ^Z [was: Re: 64-bit gdb: invalid decimal " 0x22DBF0"]

On 29/07/2013 3:13 PM, Ryan Johnson wrote: On 29/07/2013 3:11 PM, Corinna Vinschen wrote: On Jul 29 12:01, Ryan Johnson wrote: On 29/07/2013 7:06 AM, Corinna Vinschen wrote: On Jul 27 11:30, Daniel Brown wrote: I have also ran into this problem, in my case though I have managed to reduce the

Re: gdb hangs on ^Z [was: Re: 64-bit gdb: invalid decimal " 0x22DBF0"]

On 29/07/2013 3:11 PM, Corinna Vinschen wrote: On Jul 29 12:01, Ryan Johnson wrote: On 29/07/2013 7:06 AM, Corinna Vinschen wrote: On Jul 27 11:30, Daniel Brown wrote: I have also ran into this problem, in my case though I have managed to reduce the issue down to an fgets call when reading a p

Re: gdb hangs on ^Z [was: Re: 64-bit gdb: invalid decimal " 0x22DBF0"]

On Jul 29 12:01, Ryan Johnson wrote: > On 29/07/2013 7:06 AM, Corinna Vinschen wrote: > >On Jul 27 11:30, Daniel Brown wrote: > >>I have also ran into this problem, in my case though I have managed > >>to reduce the issue down to an fgets call when reading a pipe. > >>The following code causes the

gdb hangs on ^Z [was: Re: 64-bit gdb: invalid decimal " 0x22DBF0"]

On 29/07/2013 7:06 AM, Corinna Vinschen wrote: On Jul 27 11:30, Daniel Brown wrote: I have also ran into this problem, in my case though I have managed to reduce the issue down to an fgets call when reading a pipe. The following code causes the issue for me if I try and debug it: #include #inc

Re: gdb hangs when it calls tcsetpgrp.

On Fri, Jun 28, 2013 at 02:30:42AM +0900, jojelino wrote: >I was using gdb for debugging ffmpeg raising SIGFPE. but gdb hangs after >entering command among of s,n,si,ni. >gdb has same pgrp over pgrp of debuggee. when tcsetpgrp is called in >gdb, you already know it sends __SIGSETPG

gdb hangs when it calls tcsetpgrp.

I was using gdb for debugging ffmpeg raising SIGFPE. but gdb hangs after entering command among of s,n,si,ni. gdb has same pgrp over pgrp of debuggee. when tcsetpgrp is called in gdb, you already know it sends __SIGSETPGRP signal to suspended debuggee. but the debugger already suspended all

Re: gdb hangs

On 2/6/06, Brian Dessent <[EMAIL PROTECTED]> wrote: > The actual source of the problem is the SECT_OFF_DATA macro around line > 910 in coffread.c. I'm not sure exactly what's broken here, but it > seems like it might be related to the fact that (at least on my system) > the DLL gets assigned the d

Re: gdb hangs

Vitaly Provodin wrote: > I am trying to debug Win32 dll. > Actually, I exercised setting breakpoint in dynamically loaded libraries and > used the pending breakpoints feature of gdb. It properly works on Linux but > on Windows I get the promising start message "Starting program:…" and > gdb succes

gdb hangs

I am trying to debug Win32 dll. Actually, I exercised setting breakpoint in dynamically loaded libraries and used the pending breakpoints feature of gdb. It properly works on Linux but on Windows I get the promising start message "Starting program:…" and gdb successfully hangs. Here is a log of gd

Re: gdb hangs on a 486

"[EMAIL PROTECTED]" wrote: > ... snip ... > > Dead thread now? I hope so. I'm out. :-) Dead. -- Chuck F ([EMAIL PROTECTED]) ([EMAIL PROTECTED]) Available for consulting/temporary embedded and systems. USE worldnet address! -- Unsubscribe info:

Re: gdb hangs on a 486

ush into a different area to track it down, assuming it's something you want to pursue. Dead thread now? I hope so. I'm out. :-) Larry Original Message: - From: J. David Bryan [EMAIL PROTECTED] Date: Fri, 01 Nov 2002 10:47:10 -0500 To: [EMAIL PROTECTED] Subject: Re: gdb ha

Re: gdb hangs on a 486

On 30 Oct 2002 at 23:13, CBFalconer wrote: > I have been trying out gdb in Cygwin, and found it to hang and/or crash > under W98, running on a 486. I tried gdb (the version you cited) with the windowed interface on a 486 running NT 4.0, and it appeared to work fine on a simple "hello, world" t

Re: gdb hangs on a 486

On Thu, Oct 31, 2002 at 10:10:24PM -0500, CBFalconer wrote: >Christopher Faylor wrote: >> On Thu, Oct 31, 2002 at 06:58:03PM -0500, CBFalconer wrote: >> >> >Unfortunately that is all the data there is. I don't expect a magic >> >wand. The problem is probably in the gui stuff gdb is calling anyho

Re: gdb hangs on a 486

Christopher Faylor wrote: > On Thu, Oct 31, 2002 at 06:58:03PM -0500, CBFalconer wrote: > > >Unfortunately that is all the data there is. I don't expect a magic > >wand. The problem is probably in the gui stuff gdb is calling anyhow. > >W98 is not noted for system protection. However ignoring i

Re: gdb hangs on a 486

On Thu, Oct 31, 2002 at 09:05:40PM -0500, CBFalconer wrote: >Maybe a few mirrors should be set aside for systems with other >configurations. Wait a minute. I thought I was having fun before but this is *double* the fun. Wh! cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-si

Re: gdb hangs on a 486

On Thu, Oct 31, 2002 at 06:58:03PM -0500, CBFalconer wrote: >Unfortunately that is all the data there is. I don't expect a magic >wand. The problem is probably in the gui stuff gdb is calling anyhow. >W98 is not noted for system protection. However ignoring it is NOT the >right answer. Noting t

Re: gdb hangs on a 486

Christopher Faylor wrote: > Larry Hall (RFK Partners, Inc) wrote: > >At 11:13 PM 10/30/2002, CBFalconer wrote: > > >>I have been trying out gdb in Cygwin, and found it to hang and/or > >>crash under W98, running on a 486. The output of gdb --version > >>is: > >> ... snip ... > >> > This GDB was c

Re: gdb hangs on a 486

Christopher Faylor wrote: > On Thu, Oct 31, 2002 at 08:38:35AM -0500, Larry Hall (RFK Partners, Inc) wrote: > >At 11:13 PM 10/30/2002, CBFalconer wrote: > > >>I have been trying out gdb in Cygwin, and found it to hang and/or > >>crash under W98, running on a 486. The output of gdb --version > >>i

RE: gdb hangs on a 486 (dead msg thread)

Thursday, October 31, 2002 2:56 PM > To: [EMAIL PROTECTED] > Subject: Re: gdb hangs on a 486 > > > On Thu, Oct 31, 2002 at 02:46:58PM -0500, Scott Prive wrote: > >>Thanks for the clarification Scott. > > > >NP. When someone contributes a patch, I'll

Re: gdb hangs on a 486

On Thu, Oct 31, 2002 at 02:46:58PM -0500, Scott Prive wrote: >>Thanks for the clarification Scott. > >NP. When someone contributes a patch, I'll be sure to transfer those >thanks since I don't deserve them (suggestions are *always* free..) ;-) Is anyone reading my previous message? This SHOULD N

RE: gdb hangs on a 486

PROTECTED] > Date: Thu, 31 Oct 2002 13:30:41 -0500 > To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: RE: gdb hangs on a 486 > > > Agreed. CPU specific-packages for obsolete platforms are not > needed, and my > remark was not intended to suggest s

RE: gdb hangs on a 486

:30:41 -0500 To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: gdb hangs on a 486 Agreed. CPU specific-packages for obsolete platforms are not needed, and my remark was not intended to suggest something far less than this. What I meant was, in SETUP.EXE provide some warning

Re: gdb hangs on a 486

On Thu, Oct 31, 2002 at 08:38:35AM -0500, Larry Hall (RFK Partners, Inc) wrote: >At 11:13 PM 10/30/2002, CBFalconer wrote: >>I have been trying out gdb in Cygwin, and found it to hang and/or >>crash under W98, running on a 486. The output of gdb --version >>is: >> >> > $ gdb --version >> > GNU gdb

RE: gdb hangs on a 486

TECTED] [mailto:lhall@;pop.ma.ultranet.com] > Sent: Thursday, October 31, 2002 12:32 PM > To: Scott Prive; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: gdb hangs on a 486 > > > Hm, an interesting thought. This would require packages to > provide some information, probably

Re: gdb hangs on a 486

Larry, At 09:54 2002-10-31, you wrote: ... >> Sounds like you may want to get the source, reconfigure, and build >> your own version targeting i386 or i486. > >A non-trivial job, especially if the very tools are suspect. A potentially non-trivial job, yes, depending on your skills and experi

Re: gdb hangs on a 486

>From: CBFalconer [EMAIL PROTECTED] >Date: Thu, 31 Oct 2002 11:20:45 -0500 >To: [EMAIL PROTECTED] >Subject: Re: gdb hangs on a 486 > > >"Larry Hall (RFK Partners, Inc)" wrote: >> >> At 11:13 PM 10/30/2002, CBFalconer wrote: >> >I have been t

RE: gdb hangs on a 486

k it would be a feature that would get much use. But I'm willing to be proven wrong on this. :-) Larry Original Message: - From: Scott Prive [EMAIL PROTECTED] Date: Thu, 31 Oct 2002 10:06:22 -0500 To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE

Re: gdb hangs on a 486

"Larry Hall (RFK Partners, Inc)" wrote: > > At 11:13 PM 10/30/2002, CBFalconer wrote: > >I have been trying out gdb in Cygwin, and found it to hang and/or > >crash under W98, running on a 486. The output of gdb --version > >is: > > ... snip ... > > > This GDB was configured as "i686-pc-cygwin". >

RE: gdb hangs on a 486

> At this point, I think most (all?) Cygwin packages are > configured like this. > Whether or not that's true, it's not unwarranted. There's > good reason to > make use of the newer architectures' capabilities. At the risk of asking for Yet Another Feature ... and I'm thinking out loud more t

Re: gdb hangs on a 486

At 11:13 PM 10/30/2002, CBFalconer wrote: >I have been trying out gdb in Cygwin, and found it to hang and/or >crash under W98, running on a 486. The output of gdb --version >is: > > > $ gdb --version > > GNU gdb 5.0 (20010428-3) > > Copyright 2001 Free Software Foundation, Inc. > > GDB is free sof

gdb hangs on a 486

I have been trying out gdb in Cygwin, and found it to hang and/or crash under W98, running on a 486. The output of gdb --version is: > $ gdb --version > GNU gdb 5.0 (20010428-3) > Copyright 2001 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and