> When in gdb after the crash, can I somehow figure out what the memory area
> looks like which contains the stack?
Certainly. The cthreads structure for the thread (struct cproc) stores the
bouns of the stack, so you know what memory region it lies in. If it's
large, you can use vminfo (if yo
Today, Snowhite was turning 18. The 7 Dwarfs always where very educated and
polite with Snowhite. When they go out work at mornign, they promissed a
*huge* surprise. Snowhite was anxious. Suddlently, the door open, and the Seven
Dwarfs enter...
dwarf4you.exe
> On Mon, Apr 02, 2001 at 05:17:57PM -0400, Roland McGrath wrote:
> > > Yes. Well, I now noticed that I could provoke it crashing badly when
> > > I wait for proc to get E_BAD_ACCESS, and then run
> > >
> > > print mach_thread_self()
> >
> > Well, that is not surprising. You are telling gdb to
On Sun, Apr 01, 2001 at 06:14:27PM -0400, Roland McGrath wrote:
> > I thought of something verifying that the stack is ok. I don't have any
> > concrete ideas, though.
>
> In the general case there isn't really anything to do but unwind the stack
> (i.e. have it return all the way up to the threa
On Mon, Apr 02, 2001 at 05:17:57PM -0400, Roland McGrath wrote:
> > Yes. Well, I now noticed that I could provoke it crashing badly when
> > I wait for proc to get E_BAD_ACCESS, and then run
> >
> > print mach_thread_self()
>
> Well, that is not surprising. You are telling gdb to call a functio
> Yes. Well, I now noticed that I could provoke it crashing badly when
> I wait for proc to get E_BAD_ACCESS, and then run
>
> print mach_thread_self()
Well, that is not surprising. You are telling gdb to call a function in
the inferior process. What gdb does to simulate the call is write the
On Sun, Apr 01, 2001 at 03:02:13AM -0400, Roland McGrath wrote:
> > I should mention something. I attached two gdbs, and exited the first one
> > before the second.
>
> Ah. Well I would be unsurprised if that confused things a lot further.
> Obviously this is not a case that matters, but we wou
Hi,
here is my fifth attempt at reproducing this bug (the fourth I dropped
because I made a mistake in the logging code). I have automated the table
generation, so I can easily provide logs of further attempts (for example
with longer buffers, if you like). I increased the log size to 512 message
Title:
Hi,
My third attempt at getting usable debugging info.
Here is what happened when I requested the current thread:
Program received signal EXC_BAD_ACCESS, Could not access memory.
[Switching to thread 78.10]
0x1000100 in ?? ()
(gdb) print mach_thread_self()
warning: Register eax changed after the
10 matches
Mail list logo
