DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Page 2 of 2 FirstFirst 12
Results 16 to 21 of 21

Thread: Why use CDECL? / Figuring DLL API calls!

  1. #16
    Mark Alexander Bertenshaw Guest

    Re: Why use CDECL? / Figuring DLL API calls!


    "Jonathan Wood" <jwood@softcircuits.com> wrote in message
    news:3b0195af@news.devx.com...
    > Mark Alexander Bertenshaw,
    >
    > > Hmm. Tricky, this one, since I am currently attaching the debugger to
    > > Outlook Express, and pressing the Check Spelling button. I haven't

    worked
    > > out how to start tracing straight after pressing the button

    >
    > Yeah, that is tricky. I don't have an answer for you. I know there is a
    > table in the DLL that indicates how to access each exported symbol but I
    > don't know off the top of my head how to extract that information in a
    > debugger.


    Yeah, but as I was saying before, QuickView.exe can do this for your.
    Unfortunately, on Win2000 Pro, there appears to be no QuickView.exe, and if
    I try the Win98 version, I get a crash. Oh well, I suspose I better figure
    out Visual Studio again. <g>

    Cheers,

    MAB





  2. #17
    Mark Alexander Bertenshaw Guest

    Re: Why use CDECL? / Figuring DLL API calls!


    "Jonathan Wood" <jwood@softcircuits.com> wrote in message
    news:3b0195af@news.devx.com...
    > Mark Alexander Bertenshaw,
    >
    > > Hmm. Tricky, this one, since I am currently attaching the debugger to
    > > Outlook Express, and pressing the Check Spelling button. I haven't

    worked
    > > out how to start tracing straight after pressing the button

    >
    > Yeah, that is tricky. I don't have an answer for you. I know there is a
    > table in the DLL that indicates how to access each exported symbol but I
    > don't know off the top of my head how to extract that information in a
    > debugger.


    Yeah, but as I was saying before, QuickView.exe can do this for your.
    Unfortunately, on Win2000 Pro, there appears to be no QuickView.exe, and if
    I try the Win98 version, I get a crash. Oh well, I suspose I better figure
    out Visual Studio again. <g>

    Cheers,

    MAB





  3. #18
    Lobo Guest

    Re: Why use CDECL? / Figuring DLL API calls!

    Hi Mark,

    | > Yeah, that is tricky. I don't have an answer for you. I know there is a
    | > table in the DLL that indicates how to access each exported symbol but I
    | > don't know off the top of my head how to extract that information in a
    | > debugger.
    |
    | Yeah, but as I was saying before, QuickView.exe can do this for your.
    | Unfortunately, on Win2000 Pro, there appears to be no QuickView.exe,
    | and if I try the Win98 version, I get a crash. Oh well, I suspose I
    better
    | figure out Visual Studio again. <g>

    I don't know if this can help you, but, the informations given by the
    Dependency Walker utility (version 1 comes with VS, as you may know, but,
    you probably will like to get the 2nd version
    http://www.dependencywalker.com/ ], it's a very good one.) don't help you?
    I mean, you could see the preferred base address of the DLL and the entry
    point of the function and you probably would get something near where you
    want.


    --
    Abrašos,
    Lobo.
    http://www.FatorX.com.br



  4. #19
    Lobo Guest

    Re: Why use CDECL? / Figuring DLL API calls!

    Hi Mark,

    | > Yeah, that is tricky. I don't have an answer for you. I know there is a
    | > table in the DLL that indicates how to access each exported symbol but I
    | > don't know off the top of my head how to extract that information in a
    | > debugger.
    |
    | Yeah, but as I was saying before, QuickView.exe can do this for your.
    | Unfortunately, on Win2000 Pro, there appears to be no QuickView.exe,
    | and if I try the Win98 version, I get a crash. Oh well, I suspose I
    better
    | figure out Visual Studio again. <g>

    I don't know if this can help you, but, the informations given by the
    Dependency Walker utility (version 1 comes with VS, as you may know, but,
    you probably will like to get the 2nd version
    http://www.dependencywalker.com/ ], it's a very good one.) don't help you?
    I mean, you could see the preferred base address of the DLL and the entry
    point of the function and you probably would get something near where you
    want.


    --
    Abrašos,
    Lobo.
    http://www.FatorX.com.br



  5. #20
    Mark Alexander Bertenshaw Guest

    Re: Why use CDECL? / Figuring DLL API calls!


    "Lobo" <lobo_NO_SPAM_!!@fatorx.com.br> wrote:

    Lobo -

    Thanks, cool link.

    --
    Mark Alexander Bertenshaw
    Programmer/Analyst
    Chordiant Software, Inc.
    Brentford
    UK


  6. #21
    Mark Alexander Bertenshaw Guest

    Re: Why use CDECL? / Figuring DLL API calls!


    "Lobo" <lobo_NO_SPAM_!!@fatorx.com.br> wrote:

    Lobo -

    Thanks, cool link.

    --
    Mark Alexander Bertenshaw
    Programmer/Analyst
    Chordiant Software, Inc.
    Brentford
    UK


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center