I could? How do you expand a macro in VC++s debugger?

How do I know how many threads are running and which holds the lock?

/ Peter Bortas

Previous text:

2003-09-20 17:04: Subject: Win32 SMP

---

What exactly is it it fails on? You could expand SWAP_IN_THREAD_IF_REQUIRED to all its components. How many threads are there? Which holds the interpreter lock?

fmt looks messed up but maybe it's the debugger that doesn't handle varargs correctly.

/ Martin Stjernholm, Roxen IS

Doing that as we speak. Will take some time though.

/ Peter Bortas

Previous text:

2003-09-20 17:23: Subject: Win32 SMP

---

Btw, have you compiled with --with-rtldebug? If not, that's the first thing to do.

/ Martin Stjernholm, Roxen IS

Well, there is that threadview shown in the screenshot, and that one only shows one thread. Other than that I can't find anything. There is a "Step in to specific function" in the debug menu, but it's greyed out.

/ Peter Bortas

Previous text:

2003-09-20 17:22: Subject: Win32 SMP

---

You'd have to expand it either by hand or by using gcc -E, insert lots of line breaks and then recompile.

I know nothing of how the VC++ debugger works, but there got to be some way of switching to another thread to examine its stack. As for the lock, you could either call gdb_backtraces if it's possible to do that, or else you have to look at the swapped flag in the thread structs. gdb_next_thread_state in threads.c shows how to go through them.

/ Martin Stjernholm, Roxen IS

There we go

va_error(const char * 0x00447f8f, char * 0x0054216c) line 196 + 19 bytes Pike_error(const char * 0x0054216c) line 360 + 14 bytes Backend_event_handler(int 0) line 2041 + 278 bytes call_c_initializers(object * 0x004716dd) line 245 + 3 bytes debug_clone_object(program * 0x014a536c, int 0) line 311 init_backend() line 2146 low_init_main() line 815 init_modules() line 70 main(int 11, char * * 0x01300de0) line 701 PIKE! mainCRTStartup + 197 bytes KERNEL32! 77e814c7()

/ Peter Bortas

Previous text:

2003-09-20 17:12: Subject: Win32 SMP

---

Open the call stack window.

/ Martin Nilsson (saturator)

It's probably the number of bytes from the first machine instruction associated with that line. I don't think debugger cares that it's a macro.

/ Martin Stjernholm, Roxen IS

Previous text:

2003-09-20 17:34: Subject: Win32 SMP

---

I wonder how to interpret the +x bytes if the line is a macro.

You can see the threads by chosing Threads... in the Debug menu BTW.

/ Martin Nilsson (saturator)