Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "Roland Schwingel" <roland.schwingel@onevision.de>
Cc: "Mark Kettenis" <mark.kettenis@xs4all.nl>, gdb@sources.redhat.com
Subject: Re: gdb stack trace problems (Addendum)
Date: Tue, 19 Apr 2005 07:45:00 -0000	[thread overview]
Message-ID: <7468.192.87.1.200.1113896725.squirrel@192.87.1.200> (raw)
In-Reply-To: <4264B432.9000101@onevision.de>

Hi Roland,

[Dropped Dan, he's busy enough with other stuff, and he can always read it
on the list]

> Also I want to mention that it might have something to do with threading.
> In a nonthreaded app I don't have any problems with gdb 6.3.50 stack
> dumping.

Only if it links in different code, or is multi-threading still cooperative
on Windblows.  Anyway, what I really need is the disassembly for SleepEx as
implemented in the DLL.  Not the import stub, or dissassembly of some random
memory contents (the Sleep you showd is an import stub, and the call
*0xdeadbeef in it means it calls the contents of address 0xdeadbeef, not
address 0xdeadbeef itself).

Cheers,

Mark



  reply	other threads:[~2005-04-19  7:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19  7:34 Roland Schwingel
2005-04-19  7:45 ` Mark Kettenis [this message]
2005-04-19  8:01 Roland Schwingel
     [not found] ` <4268B942.5080300@onevision.de>
2005-04-22 17:51   ` Mark Kettenis
2005-04-25 12:35 Roland Schwingel
2005-04-25  8:00 ` Roland Schwingel
2005-04-25 19:35 ` Mark Kettenis
2005-04-25 19:45   ` Daniel Jacobowitz
2005-04-25 20:37     ` Mark Kettenis
2005-04-26  9:11 Roland Schwingel
2005-04-26 11:53 Roland Schwingel
2005-05-02  7:04 Roland Schwingel
2005-05-08 13:31 ` Mark Kettenis
2005-05-08 23:20   ` Christopher Faylor
2005-05-09  4:48     ` Eli Zaretskii
2005-05-09  5:26       ` Christopher Faylor
2005-05-09  5:30     ` Stan Shebs
2005-05-10  8:38 Roland Schwingel
2005-05-10  8:39 Roland Schwingel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7468.192.87.1.200.1113896725.squirrel@192.87.1.200 \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb@sources.redhat.com \
    --cc=roland.schwingel@onevision.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox