Mail Archives: cygwin/2001/02/22/10:54:15
On Thu, Feb 22, 2001 at 08:48:07AM -0500, Earnie Boyd wrote:
>Christopher Faylor wrote:
>>
>> On Wed, Feb 21, 2001 at 06:43:40PM -0800, Kevin Camera wrote:
>> >Thanks for the tip. In fact, the debugger was in thread 1, and the only
>> >other thread did not offer any other information. So unfortunately the
>> >problem was with the compiler or debugger, since all threads had no trace
>> >information.
>>
>> Hmm. As someone who uses the compiler and debugger on an almost daily basis
>> I have to say that I have never seen this behavior on a program that was
>> compiled with debugging info (-g).
>>
>
>Well, I can't say that I use GDB that often but everytime that I've used
>it I see this problem. I've been able to switch to the assembler
>listing and set breakpoints on each instruction of the object containing
>main() and be able to get a source code point of problem.
I'm not interested in fixing the GDB problem. It works fine for me when
I need it.
If someone wants to track this down, more power to them.
I assume it has something to do with the frame pointer not being set.
I'm beginning to wonder if the rumors of Cygwin's death are not
exaggerated if two notable Cygwin contributors have resorted to sending
"me too" and "here's a simple test case, hope that helps" messages.
Corinna (and Chuck and Egor) and I can't do everything. If you want a
fix for the problem, roll up your sleeves and fix it!
cgf
(This post will now be followed by the obligatory "I would look into this
but I don't know how to debug gdb" or "I really don't have the time"
excuses.)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -