From: Marc S. <ma...@au...> - 2001-04-20 22:03:54
|
You're apparently not the first to hit this sort of thing. From the GDB-bug archives.... (The compiler-related tools are the only ones where we didn't produce the binaries ourselves - Cygnus produced them - so I don't know which exact options that they used.) ------------------------------------------------------------------------ Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index] Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next] Re: Can't restore frame ... error in the GDB * To: "K. Young Park" <pkyoung at palmpalm dot co dot kr> * Subject: Re: [ECOS] Can't restore frame ... error in the GDB * From: Jonathan Larmour <jlarmour at redhat dot com> * Date: Fri, 23 Feb 2001 19:49:58 +0000 * Cc: ecos-discuss at sources dot redhat dot com * Organization: Red Hat UK Ltd. * References: <04e201c09c78$c848d9c0$280...@pa...> ------------------------------------------------------------------------ "K. Young Park" wrote: > > Hi, > I have succeeded in porting the redboot to my SA-1110 based board. Thanks for all the replies you have given to me. > I am now running some examples via the GDB remote debugging. > By the way when I run such code as twothreads in the example directory, > I sometimes see the message box saying "Couldn't restore frame in current thread, at frame 0". Though the code seems to run even after the message. > What's the meaning of this message? Did I make any mistake while the porting process? Not necessarily. You could try adding -mapcs-frame to the CYGBLD_GLOBAL_CFLAGS option. You could also try reducing the optimization level from -O2 to -O1 or disable it (-O0) just to see if that makes a difference; or you could also try disabling the CDL options CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM and CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT Let us know if one of those fixes things for you. Jifl > > Whenever I try to display threads in gdb, I get a message box popping up > with the text "Couldn't restore frame in current thread, at frame 0". I > click OK, and a window comes up with the title "Processes" and Thread 1 > listed. The error pops up every time I step in the debugger until I close > the "Processes" window, then everything seems to work fine. Is this a bug, > or do I need to adjust my build? I'm compiling with these options > currently: > > g++ -c -gxcoff -fhuge-objects -mthreads ... > g++ -gxcoff -mthreads -Xlinker -bbigtoc ... > > Is there anything I need to add to these options? > > Thanks, > Mike Allen > _______________________________________________ > aixtoolbox-list mailing list > aix...@os... > http://oss.software.ibm.com/developerworks/opensource/mailman/listinfo/aixtoolbox-list > -- Marc Stephenson IBM Server Group - Austin, TX Internet: ma...@au... NOTES: ma...@us... Phone: 512-327-5670 T/L 678-3189 |