On Dec 8, 9:42am, [EMAIL PROTECTED] wrote:
> I am getting a segmentation violation with gdb that occurs when I
> try to set a break point for my traced program right after
> loading the program into gdb, but before trying to execute/trace
> the program itself. I noticed the problem when I originally was
> getting a segv with gdb while tracing the program,
> which had hit a segv itself, and gdb died when I tried
> to get a stack back trace on my halted program.
>
> I can't reproduce this with a toy program and I can run gdb on
> itself OK.
In order to track this down, I will need a test program. (It doesn't
necessarily need to be a toy program...)
> At first glance it looks like we are stuck in a recursive cycle
> that eventually overflows the stack, and even though
> it looks like this cycling is typically done with another
> toy program I've traced, there are at least 100K stack
> records here in this cycle (and I'm still counting).
I agree; it does look this way.
Kevin
_______________________________________________
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb
