Re: system files access

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



On Fri, 9 Sep 2005 14:52:02 -0700, tb2000
<tb2000@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>Steve, thanks.
>
>The first module asked for was I think a coredll.

I _think_ this is relevant, but I'm not quite sure:
When I debug, the debugger sometimes pops up a dialog asking for
source code to coredll or some other system library. I dismiss the
dialog and continue with no problems. I'm so used to it I can't
remember details. I'm quite sure that the only thing I lose by
dismissing the dialog is the ability to step through the source code
of functions in that module; no loss for me. I know this question has
been asked and answered, but just failed in my attempt to use google
to find relevant threads. I'm quite sure one answer provided methods
for suppressing the dialog; maybe something to do with the option to
show the assembly window.


>
>I am trying if I can attach the debugger to a CMD process, thinking that I
>could debug a piece of code that was actually started from a telnet window.
>Maybe wild - just trying to get going...
>
>The reason for doing this is that I am working on a library which I am
>debugging with some user input from CMD. When I do this in a telnet session,
>I have no problems (without of cause having the debugger). If I start the
>debugger on the device, a cmd windows pops up and the app locks from a
>getchar() command. Trying to wrap this in an independent thread did not help
>either. If I issue <char>+cr sequences, the lock is temporarily released and
>the system comes alive again.
>
>Any suggestions? Thanks!
>
>Here's some of the code:
>
>.
>.
>
>int WINAPI WinMain( HINSTANCE hInstance,
> HINSTANCE hPrevInstance,
> LPTSTR lpCmdLine,
> int nCmdShow)
>{
> int key = 0, mykey = 0;
>
> Thread *keywrapper;
> keywrapper = cg_keywrapper_new();
> keywrapper->userData=&key;
> key = 0; mykey = 0;
> do {
> if (key) {
> mykey=key;
> key=0;
> printf("*%X*%X",key,mykey);
> switch (mykey) {
> case 'P':
> ...
> break;
> case 'X':
> break;
> default:
> PrintKeyMessage();
> }
> } else {
> sleep(0); //control back to task scheduler
> }
> } while( mykey != 'X');
>
> keywrapper_delete(keywrapper);
> return(0);
>}
>
>
>"Steve Maillet (eMVP)" wrote:
>
>> It's not actually looking for the file - it's looking for the debug symbols.
>> The IDE should be able to locate them automatically - what modules are
>> giving you this problem?
>>
>> --
>> Steve Maillet
>> EmbeddedFusion
>> www.EmbeddedFusion.com
>> smaillet at EmbeddedFusion dot com
>>
>>
>>

-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
500 Harrison Ave., Suite 3R
Boston, MA 02118
www.penfact.com
.



Relevant Pages

  • RE: debugging dynamic code
    ... Cordbg.exe that ships with the framework SDK (including source code I ... the debugger must be inside my app, so iI need to have a debugger that dubug ... depends on how you are referencing your dependant assemblies. ... compile it and debug it. ...
    (microsoft.public.dotnet.framework.clr)
  • Re: Seg fault even though address space is accessible
    ... There's a guy around here somewhere who can debug your problem (no ... matter what it is) using only the debugger. ... debugger and not seeing the source code. ... I did extend the position held by one of the trolls that the debugger ...
    (comp.lang.c)
  • Re: Procyon Library for Atmel AVR MCU - =?utf-8?Q?I=C2=B2C?= problems
    ... Including the one that he can debug any program ... without source code, provided that he has a debugger - or was that the ... don't you find your double standards embarrassing? ...
    (comp.lang.c)
  • RE: debugging dynamic code
    ... Cordbg.exe that ships with the framework SDK (including source code I ... the debugger must be inside my app, so iI need to have a debugger that dubug ... depends on how you are referencing your dependant assemblies. ... compile it and debug it. ...
    (microsoft.public.dotnet.framework.clr)
  • Re: How to connect to children process
    ... Main problem is amount of manual operations required per debug cycle. ... connection to DLL with debugger takes sensible amount of time and manual ... Is the main problem that the debugger keeps symbols file loaded ... AFAIK that's how VS2003 debugger works, but WinDbg should usually ...
    (microsoft.public.vsnet.debugging)