gdb trouble

gdb trouble

[vipin aravind]

[-- Attachment #1.1: Type: text/plain, Size: 386 bytes --]

hi,
I have done
1)gcc -g  test.c
2)  gdb 
3)   from the  "run"  menu I choose  the executeable  I get  the following error-message box.



---------------------------
Error
---------------------------
Error loading "/home/Administrator/test":
 not in executable format: File format not recognized

---------------------------
OK   
---------------------------

vipin

[-- Attachment #1.2: Type: text/html, Size: 1212 bytes --]

[-- Attachment #2: InterScan_Disclaimer.txt --]
[-- Type: text/plain, Size: 856 bytes --]

-------------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------


[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Corinna Vinschen]

On Tue, Nov 20, 2001 at 01:49:27PM +0530, vipin aravind wrote:
> hi,
> I have done
> 1)gcc -g  test.c
> 2)  gdb 
> 3)   from the  "run"  menu I choose  the executeable  I get  the following error-message box.
> 
> 
> 
> ---------------------------
> Error
> ---------------------------
> Error loading "/home/Administrator/test":
>  not in executable format: File format not recognized

The gdb GUI is not Cygwin path aware, unfortunately.  Try the
same w/o GUI by starting `gdb -nw'

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Keith Seitz]

On Tue, 20 Nov 2001, Corinna Vinschen wrote:

> The gdb GUI is not Cygwin path aware, unfortunately.  Try the
> same w/o GUI by starting `gdb -nw'

In what way is it not "path aware"?

Keith



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Peter Buckley]

I presuppose that it doesn't understand /cygdrive and mount points, so 
it doesn't compute /usr/bin to mean c:\cygwin\bin.

Wild guess-
Peter

Keith Seitz wrote:

> On Tue, 20 Nov 2001, Corinna Vinschen wrote:
> 
> 
>>The gdb GUI is not Cygwin path aware, unfortunately.  Try the
>>same w/o GUI by starting `gdb -nw'
>>
> 
> In what way is it not "path aware"?
> 
> Keith
> 
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 


-- 
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]

--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Keith Seitz]

On Tue, 20 Nov 2001, Peter Buckley wrote:

> I presuppose that it doesn't understand /cygdrive and mount points, so
> it doesn't compute /usr/bin to mean c:\cygwin\bin.

Probably not a bad guess, but allow me to enumerate what Insight can and
cannot do (for the record). At least as far as I know:

When using the file menu's Open option, users open an exe for debugging by
using the Window's file selection dialog, which knows nothing about
cygwin (of course).

When using the console window to specify filenames, it is (or should be)
100% aware that /bin is c:/cygwin/bin, just as gdb does (or should).

I'm not sure where else command-line gdb and Insight differ w.r.t.
filenames (which is why I asked my original question).

Of course, I could be missing something obvious.
Keith


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[David A. Cobb]

Peter Buckley wrote:

> I presuppose that it doesn't understand /cygdrive and mount points, so 
> it doesn't compute /usr/bin to mean c:\cygwin\bin.


Now I'm totally confused [i.e. more than usually so].
Why does the APPLICATION need to be "Cygwin aware?"  If it references 
"/usr/bin" the equation to "C:\cygwin\bin" or whatever is entirely 
behind the curtains, nicht war?

Please, Corinna, clarify what gdb is "missing."


> 
> Wild guess-
> Peter
> 
> Keith Seitz wrote:
> 
>> On Tue, 20 Nov 2001, Corinna Vinschen wrote:
>>
>>
>>> The gdb GUI is not Cygwin path aware, unfortunately.  Try the
>>> same w/o GUI by starting `gdb -nw'
>>>
>>
>> In what way is it not "path aware"?
>>
>> Keith
>>
>>
>>
>> -- 
>> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>> Bug reporting:         http://cygwin.com/bugs.html
>> Documentation:         http://cygwin.com/docs.html
>> FAQ:                   http://cygwin.com/faq/
>>
>>
> 
> 


-- 
David A. Cobb, Software Engineer, Public Access Advocate, All around 
nice guy.
New PGP key 09/13/2001:
:<http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=superbiskit&\
fingerprint=on>
:<http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=superbiskit&\
fingerprint=on>
Fingerprint=0x{E7C6_4EE2_6B75_5BA3_C52E__77FA_63C3_9366_DCFB_229B}
"By God's Grace I am a Christian man, by my actions a great sinner."
--The Way of a Pilgrim, R. M. French [tr.]
Potentially Viral Software is any software for which you are not allowed
to examine the source.  Do not buy or use Potentially Viral Software!


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Corinna Vinschen]

On Tue, Nov 20, 2001 at 11:36:20AM -0500, David A. Cobb wrote:
> Peter Buckley wrote:
> 
> > I presuppose that it doesn't understand /cygdrive and mount points, so 
> > it doesn't compute /usr/bin to mean c:\cygwin\bin.
> 
> 
> Now I'm totally confused [i.e. more than usually so].
> Why does the APPLICATION need to be "Cygwin aware?"  If it references 
> "/usr/bin" the equation to "C:\cygwin\bin" or whatever is entirely 
> behind the curtains, nicht war?
> 
> Please, Corinna, clarify what gdb is "missing."

gdb is a Cygwin application.  It can act using POSIX paths and
Cygwin mount points.  The GUI is not a Cygwin app.  It acts 
using native Windows paths.  Nobody has ported that stuff to
Cygwin so far.  AFAIK.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Keith Seitz]

On Tue, 20 Nov 2001, Corinna Vinschen wrote:

> gdb is a Cygwin application.  It can act using POSIX paths and
> Cygwin mount points.  The GUI is not a Cygwin app.  It acts
> using native Windows paths.  Nobody has ported that stuff to
> Cygwin so far.  AFAIK.

Ok, now you can add me to the confused list, too.

Insight (I assume this is the GUI gdb we're talking about?) is built on
gdb. Gdb is a cygwin app, and, therefore, Insight is, too.

In both apps, I can type "file /home/keiths/foo.exe" and it will load
C:\Cygwin\home\keiths\foo.exe. Is this not cygwin-awareness?

What does NOT work, however, is Tcl. The tcl interp in Insight is _not_
cygwin aware, so you cannot do something like:

  (gdb) tk file stat /home/keiths/foo.exe

Instead, you need to use something like:

  (gdb) tk file stat [ide_cygwin_path to_win32 /home/keiths/foo.exe]

??
Keith



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Corinna Vinschen]

On Tue, Nov 20, 2001 at 10:17:20AM -0800, Keith Seitz wrote:
> On Tue, 20 Nov 2001, Corinna Vinschen wrote:
> 
> > gdb is a Cygwin application.  It can act using POSIX paths and
> > Cygwin mount points.  The GUI is not a Cygwin app.  It acts
> > using native Windows paths.  Nobody has ported that stuff to
> > Cygwin so far.  AFAIK.
> 
> Ok, now you can add me to the confused list, too.

Yeah, me too.  What I told was based on what you've written
in your previous posting.  I have no real clue of the GUI
since I'm always using gdb -nw.  You should know that better
than me so please explain it.

Corinna

> Insight (I assume this is the GUI gdb we're talking about?) is built on
> gdb. Gdb is a cygwin app, and, therefore, Insight is, too.
> 
> In both apps, I can type "file /home/keiths/foo.exe" and it will load
> C:\Cygwin\home\keiths\foo.exe. Is this not cygwin-awareness?
> 
> What does NOT work, however, is Tcl. The tcl interp in Insight is _not_
> cygwin aware, so you cannot do something like:
> 
>   (gdb) tk file stat /home/keiths/foo.exe
> 
> Instead, you need to use something like:
> 
>   (gdb) tk file stat [ide_cygwin_path to_win32 /home/keiths/foo.exe]
> 
> ??
> Keith

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Keith Seitz]

On Tue, 20 Nov 2001, Corinna Vinschen wrote:

> On Tue, Nov 20, 2001 at 10:17:20AM -0800, Keith Seitz wrote:
> > On Tue, 20 Nov 2001, Corinna Vinschen wrote:
> >
> > > gdb is a Cygwin application.  It can act using POSIX paths and
> > > Cygwin mount points.  The GUI is not a Cygwin app.  It acts
> > > using native Windows paths.  Nobody has ported that stuff to
> > > Cygwin so far.  AFAIK.
> >
> > Ok, now you can add me to the confused list, too.
>
> Yeah, me too.  What I told was based on what you've written
> in your previous posting.  I have no real clue of the GUI
> since I'm always using gdb -nw.  You should know that better
> than me so please explain it.

Hmm. Okay.

So that we're all on the same page:

- Insight/gdb are both cygwin-aware. If you type commands at the console
using filenames, these filenames will go through all the cygwin mounts and
such.

- The tcl interpreter in Insight is NOT cygwin-aware. If you write custom
tcl commands for use with Insight, you must be careful to use
"ide_cygwin_path" to convert to/from cygwin paths from/to windows paths.

I think that's all there is.

Feeling less confused now. :v)
Keith



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Vincent Girard-Reydet]

I have tried your link, but it's a dead link. I saw your post telling that
MSDN CDs provide teh CV5.0 spec. I can find them neither on the last MSDN
library CDrom. Any idea of where I could find the spec ?

Vincent Girard-Reydet

----- Original Message -----
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Robert Collins" <robert.collins@itdomain.com.au>; "Corinna
Vinschen" <cygwin@cygwin.com>
Sent: Wednesday, November 21, 2001 9:42 PM
Subject: Re: gdb trouble

Found it.

http://www.pearsonptg.com/book_detail/0,3771,0201721872,00.html

claims to document the pdb format.

Rob
===
----- Original Message -----
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Robert Collins" <robert.collins@itdomain.com.au>; "Corinna
Vinschen" <cygwin@cygwin.com>
Sent: Wednesday, November 21, 2001 9:42 PM
Subject: Re: gdb trouble


> And more (last one I think)
>
> Watcomm apparent support Codeview in their debug formats - and they
are
> open sourcing watcomm C/C++ - see http://www.openwatcom.org/
>
> Rob
> ===
> ----- Original Message -----
> From: "Robert Collins" <robert.collins@itdomain.com.au>
> To: "Robert Collins" <robert.collins@itdomain.com.au>; "Corinna
> Vinschen" <cygwin@cygwin.com>
> Sent: Wednesday, November 21, 2001 9:36 PM
> Subject: Re: gdb trouble
>
>
> > And some more that caught my eye:
> >
>
http://www.microsoft.com/msj/defaultframe.asp?page=/msj/0399/hood/hood03
> > 99.htm&nav=/msj/0399/newnav.htm
> > Is an article about .dbg file formats - not written my MS, and
> includdes
> > references to pdb.
> > It also has a handy file cvinfo.h which is the header required to
> > manipulate codeview 4 data.
> >
> > MSDN returns a hit on COFFTOCV.C which does what it says.
> >
> > http://www.winehq.com/hypermail/wine-patches/2001/08/0106.html
> > based on the info from the above header!
> >
> > http://support.microsoft.com/support/kb/articles/q121/3/66.asp
> >
> > These folk appear to be able to generate Codeview data (which is
what
> is
> > in pdb files).
> > http://www.digitalmars.com/faq.html
> > and http://www.digitalmars.com/bibliography.html (see CV4)
> >
> > Wine has/had pdb partial support
> > http://www.winehq.com/News/1999-49.html
> >
> > http://www.tbcnet.com/~clive/vcomwinp.html
> > has a dumppe that understands codeview
> >
> > http://www.rdbooks.com/store/products/rd2364.htm is an old book -
> maybe
> > there is a newer version with CV4 info?
> >
> > http://www.wotsit.org/
> > is a useful site on file formats - nothing there, but if you ask,
> maybe
> > they know where to find it.
> >
> > Codeview is also known as CV4 - a earch on that might help.
> > MSDN spat out this:
> > http://support.microsoft.com/support/kb/articles/Q194/9/21.ASP
> > which has some partial info on the Codeview format.
> >
> > http://www.jorgon.freeserve.co.uk/GobugHelp/Symbolic.htm
> > isn't really helpful, butmay be of interest
> >
> > Lastly, MSDN CD roms do have the Specification (CV5.0 Symbolic Debug
> > Information) But I'm afraid to open it :]. Perhaps someone you know
> can
> > create a clean room spec for you.
> >
> > Rob
> >
> > ===
> > ----- Original Message -----
> > From: "Robert Collins" <robert.collins@itdomain.com.au>
> > To: "Corinna Vinschen" <cygwin@cygwin.com>
> > Sent: Wednesday, November 21, 2001 8:46 PM
> > Subject: Re: gdb trouble
> >
> >
> > > Some related articles:
> > >
> > > http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
> > >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
> > > /html/msdn_peeringpe.asp
> > >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
> > > bghelp_0l0n.asp?frame=true
> > >
> > > To me it looks like there are 2 options.
> > > 1) add the user of the symbol handling library to gdb. That should
> > allow
> > > pdb use.
> > > 2) Using the symbol handling library, and (say) VC++, generate
test
> > > exe's with .pdb and reverse engineer the format. Once done, use
the
> > > resulting library in gdb.
> > >
> > > Rob
> > >
> > >
> > > ===
> > > ----- Original Message -----
> > > From: "Corinna Vinschen" <cygwin@cygwin.com>
> > > To: "cygwin" <cygwin@cygwin.com>
> > > Sent: Wednesday, November 21, 2001 8:29 PM
> > > Subject: Re: gdb trouble
> > >
> > >
> > > > On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > > > > I  had  been using  softice  debugger  on windows  which  is
> from
> > > > > mega(  and  it understands pdb  format)  and  how   do they
know
> > > the
> > > > > format?
> > > > > I  think  it  would  be documented.
> > > >
> > > > Sure.  Somewhere.  Under NDA, I assume.
> > > >
> > > > Corinna
> > > >
> > > > --
> > > > Corinna Vinschen                  Please, send mails regarding
> > Cygwin
> > > to
> > > > Cygwin Developer
> > > mailto:cygwin@cygwin.com
> > > > Red Hat, Inc.
> > > >
> > > > --
> > > > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > > > Bug reporting:         http://cygwin.com/bugs.html
> > > > Documentation:         http://cygwin.com/docs.html
> > > > FAQ:                   http://cygwin.com/faq/
> > > >
> > > >
> > >
> > >
> > > --
> > > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > > Bug reporting:         http://cygwin.com/bugs.html
> > > Documentation:         http://cygwin.com/docs.html
> > > FAQ:                   http://cygwin.com/faq/
> > >
> > >
> >
> >
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Katherina O'Connor]

[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]

... ".pch" is a suffix for "pre-compiled" header
files, a feature which is optionally, having 
nothing to do with debug. MSVC can generate debug 
information either in a MS format or COFF. Not
"understanding" COFF is a problem of gdb 
and not of MSVC.

-Kathy

Not really. Microsoft is using a proprietary debug format 



On Tue, Nov 20, 2001 at 01:52:20PM +0530, vipin aravind wrote:
> oops sorry the executeable was created as a.exe and gdb a worked
> How do I get the prefix same as the source file.

gcc -o outputfilename ...

> Is it possible to debug vc++ generated exe's?

Not really. Microsoft is using a proprietary debug format (.pch files).
You would be stuck with assembler debugging.

Corinna

-- 
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/




______________________________________________________
Kein Schwein klickt mich an? Tragen Sie Ihre Site doch einfach im
Fireballkatalog ein! http://www.fireball.de/katalogeintrag.html




[-- Attachment #2: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Corinna Vinschen]

On Tue, Nov 20, 2001 at 05:43:22AM -0800, Katherina O'Connor wrote:
> ... ".pch" is a suffix for "pre-compiled" header
> files, a feature which is optionally, having 
> nothing to do with debug. MSVC can generate debug 

Sorry, I meant the .pdb files or whatever the extension is.  The
format of these files is nowhere documented.

> information either in a MS format or COFF. Not
> "understanding" COFF is a problem of gdb 
> and not of MSVC.

gdb understands coff but isn't that only generated by VC when
giving some special option?  I don't have VC installed anywhere.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[vipin aravind]

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

I  had  been using  softice  debugger  on windows  which  is from
mega(  and  it understands pdb  format)  and  how   do they know  the
format?
I  think  it  would  be documented.
vipin
----- Original Message -----
From: "Corinna Vinschen" <cygwin@cygwin.com>
To: <cygwin@cygwin.com>
Sent: Tuesday, November 20, 2001 7:35 PM
Subject: Re: gdb trouble


> On Tue, Nov 20, 2001 at 05:43:22AM -0800, Katherina O'Connor wrote:
> > ... ".pch" is a suffix for "pre-compiled" header
> > files, a feature which is optionally, having
> > nothing to do with debug. MSVC can generate debug
>
> Sorry, I meant the .pdb files or whatever the extension is.  The
> format of these files is nowhere documented.
>
> > information either in a MS format or COFF. Not
> > "understanding" COFF is a problem of gdb
> > and not of MSVC.
>
> gdb understands coff but isn't that only generated by VC when
> giving some special option?  I don't have VC installed anywhere.
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Developer                                mailto:cygwin@cygwin.com
> Red Hat, Inc.
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>


[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 854 bytes --]

----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------



[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Larry Hall (RFK Partners, Inc)]

Well if you can point us to documentation, I expect folks here would 
be happy and willing to read it.

Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



At 11:44 PM 11/20/2001, vipin aravind wrote:
>I  had  been using  softice  debugger  on windows  which  is from
>mega(  and  it understands pdb  format)  and  how   do they know  the
>format?
>I  think  it  would  be documented.
>vipin
>----- Original Message -----
>From: "Corinna Vinschen" <cygwin@cygwin.com>
>To: <cygwin@cygwin.com>
>Sent: Tuesday, November 20, 2001 7:35 PM
>Subject: Re: gdb trouble
>
>
> > On Tue, Nov 20, 2001 at 05:43:22AM -0800, Katherina O'Connor wrote:
> > > ... ".pch" is a suffix for "pre-compiled" header
> > > files, a feature which is optionally, having
> > > nothing to do with debug. MSVC can generate debug
> >
> > Sorry, I meant the .pdb files or whatever the extension is.  The
> > format of these files is nowhere documented.
> >
> > > information either in a MS format or COFF. Not
> > > "understanding" COFF is a problem of gdb
> > > and not of MSVC.
> >
> > gdb understands coff but isn't that only generated by VC when
> > giving some special option?  I don't have VC installed anywhere.
> >
> > Corinna
> >
> > --
> > Corinna Vinschen                  Please, send mails regarding Cygwin to
> > Cygwin Developer                                mailto:cygwin@cygwin.com
> > Red Hat, Inc.
> >
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting:         http://cygwin.com/bugs.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> >
>
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/ 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Corinna Vinschen]

On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> I  had  been using  softice  debugger  on windows  which  is from
> mega(  and  it understands pdb  format)  and  how   do they know  the
> format?
> I  think  it  would  be documented.

Sure.  Somewhere.  Under NDA, I assume.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Robert Collins]

Some related articles:

http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
/html/msdn_peeringpe.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
bghelp_0l0n.asp?frame=true

To me it looks like there are 2 options.
1) add the user of the symbol handling library to gdb. That should allow
pdb use.
2) Using the symbol handling library, and (say) VC++, generate test
exe's with .pdb and reverse engineer the format. Once done, use the
resulting library in gdb.

Rob


===
----- Original Message -----
From: "Corinna Vinschen" <cygwin@cygwin.com>
To: "cygwin" <cygwin@cygwin.com>
Sent: Wednesday, November 21, 2001 8:29 PM
Subject: Re: gdb trouble


> On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > I  had  been using  softice  debugger  on windows  which  is from
> > mega(  and  it understands pdb  format)  and  how   do they know
the
> > format?
> > I  think  it  would  be documented.
>
> Sure.  Somewhere.  Under NDA, I assume.
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin
to
> Cygwin Developer
mailto:cygwin@cygwin.com
> Red Hat, Inc.
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[vipin aravind]

[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]


well  I  read in an msdn article  that the pdb  format is not  publicly
documented.  probably numega  got  in some  sort of
agreement  with microsoft  on  providing  the info.
vipin


> Some related articles:
>
> http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
> /html/msdn_peeringpe.asp
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
> bghelp_0l0n.asp?frame=true
>
> To me it looks like there are 2 options.
> 1) add the user of the symbol handling library to gdb. That should allow
> pdb use.
> 2) Using the symbol handling library, and (say) VC++, generate test
> exe's with .pdb and reverse engineer the format. Once done, use the
> resulting library in gdb.
>
> Rob
>
>
> ===
> ----- Original Message -----
> From: "Corinna Vinschen" <cygwin@cygwin.com>
> To: "cygwin" <cygwin@cygwin.com>
> Sent: Wednesday, November 21, 2001 8:29 PM
> Subject: Re: gdb trouble
>
>
> > On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > > I  had  been using  softice  debugger  on windows  which  is from
> > > mega(  and  it understands pdb  format)  and  how   do they know
> the
> > > format?
> > > I  think  it  would  be documented.
> >
> > Sure.  Somewhere.  Under NDA, I assume.
> >
> > Corinna
> >
> > --
> > Corinna Vinschen                  Please, send mails regarding Cygwin
> to
> > Cygwin Developer
> mailto:cygwin@cygwin.com
> > Red Hat, Inc.
> >
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting:         http://cygwin.com/bugs.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> >
> >
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>


[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 854 bytes --]

----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------



[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[vipin aravind]

well  I  read in an msdn article  that the pdb  format is not  publicly
documented.  probably numega  got  in some  sort of
agreement  with microsoft  on  providing  the info.
vipin


> Some related articles:
>
> http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
> /html/msdn_peeringpe.asp
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
> bghelp_0l0n.asp?frame=true
>
> To me it looks like there are 2 options.
> 1) add the user of the symbol handling library to gdb. That should allow
> pdb use.
> 2) Using the symbol handling library, and (say) VC++, generate test
> exe's with .pdb and reverse engineer the format. Once done, use the
> resulting library in gdb.
>
> Rob
>
>
> ===
> ----- Original Message -----
> From: "Corinna Vinschen" <cygwin@cygwin.com>
> To: "cygwin" <cygwin@cygwin.com>
> Sent: Wednesday, November 21, 2001 8:29 PM
> Subject: Re: gdb trouble
>
>
> > On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > > I  had  been using  softice  debugger  on windows  which  is from
> > > mega(  and  it understands pdb  format)  and  how   do they know
> the
> > > format?
> > > I  think  it  would  be documented.
> >
> > Sure.  Somewhere.  Under NDA, I assume.
> >
> > Corinna
> >
> > --
> > Corinna Vinschen                  Please, send mails regarding Cygwin
> to
> > Cygwin Developer
> mailto:cygwin@cygwin.com
> > Red Hat, Inc.
> >
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting:         http://cygwin.com/bugs.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> >
> >
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>

Re: gdb trouble

[Robert Collins]

And some more that caught my eye:
http://www.microsoft.com/msj/defaultframe.asp?page=/msj/0399/hood/hood03
99.htm&nav=/msj/0399/newnav.htm
Is an article about .dbg file formats - not written my MS, and includdes
references to pdb.
It also has a handy file cvinfo.h which is the header required to
manipulate codeview 4 data.

MSDN returns a hit on COFFTOCV.C which does what it says.

http://www.winehq.com/hypermail/wine-patches/2001/08/0106.html
based on the info from the above header!

http://support.microsoft.com/support/kb/articles/q121/3/66.asp

These folk appear to be able to generate Codeview data (which is what is
in pdb files).
http://www.digitalmars.com/faq.html
and http://www.digitalmars.com/bibliography.html (see CV4)

Wine has/had pdb partial support
http://www.winehq.com/News/1999-49.html

http://www.tbcnet.com/~clive/vcomwinp.html
has a dumppe that understands codeview

http://www.rdbooks.com/store/products/rd2364.htm is an old book - maybe
there is a newer version with CV4 info?

http://www.wotsit.org/
is a useful site on file formats - nothing there, but if you ask, maybe
they know where to find it.

Codeview is also known as CV4 - a earch on that might help.
MSDN spat out this:
http://support.microsoft.com/support/kb/articles/Q194/9/21.ASP
which has some partial info on the Codeview format.

http://www.jorgon.freeserve.co.uk/GobugHelp/Symbolic.htm
isn't really helpful, butmay be of interest

Lastly, MSDN CD roms do have the Specification (CV5.0 Symbolic Debug
Information) But I'm afraid to open it :]. Perhaps someone you know can
create a clean room spec for you.

Rob

===
----- Original Message -----
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Corinna Vinschen" <cygwin@cygwin.com>
Sent: Wednesday, November 21, 2001 8:46 PM
Subject: Re: gdb trouble


> Some related articles:
>
> http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
> /html/msdn_peeringpe.asp
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
> bghelp_0l0n.asp?frame=true
>
> To me it looks like there are 2 options.
> 1) add the user of the symbol handling library to gdb. That should
allow
> pdb use.
> 2) Using the symbol handling library, and (say) VC++, generate test
> exe's with .pdb and reverse engineer the format. Once done, use the
> resulting library in gdb.
>
> Rob
>
>
> ===
> ----- Original Message -----
> From: "Corinna Vinschen" <cygwin@cygwin.com>
> To: "cygwin" <cygwin@cygwin.com>
> Sent: Wednesday, November 21, 2001 8:29 PM
> Subject: Re: gdb trouble
>
>
> > On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > > I  had  been using  softice  debugger  on windows  which  is from
> > > mega(  and  it understands pdb  format)  and  how   do they know
> the
> > > format?
> > > I  think  it  would  be documented.
> >
> > Sure.  Somewhere.  Under NDA, I assume.
> >
> > Corinna
> >
> > --
> > Corinna Vinschen                  Please, send mails regarding
Cygwin
> to
> > Cygwin Developer
> mailto:cygwin@cygwin.com
> > Red Hat, Inc.
> >
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting:         http://cygwin.com/bugs.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> >
> >
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Robert Collins]

And more (last one I think)

Watcomm apparent support Codeview in their debug formats - and they are
open sourcing watcomm C/C++ - see http://www.openwatcom.org/

Rob
===
----- Original Message -----
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Robert Collins" <robert.collins@itdomain.com.au>; "Corinna
Vinschen" <cygwin@cygwin.com>
Sent: Wednesday, November 21, 2001 9:36 PM
Subject: Re: gdb trouble


> And some more that caught my eye:
>
http://www.microsoft.com/msj/defaultframe.asp?page=/msj/0399/hood/hood03
> 99.htm&nav=/msj/0399/newnav.htm
> Is an article about .dbg file formats - not written my MS, and
includdes
> references to pdb.
> It also has a handy file cvinfo.h which is the header required to
> manipulate codeview 4 data.
>
> MSDN returns a hit on COFFTOCV.C which does what it says.
>
> http://www.winehq.com/hypermail/wine-patches/2001/08/0106.html
> based on the info from the above header!
>
> http://support.microsoft.com/support/kb/articles/q121/3/66.asp
>
> These folk appear to be able to generate Codeview data (which is what
is
> in pdb files).
> http://www.digitalmars.com/faq.html
> and http://www.digitalmars.com/bibliography.html (see CV4)
>
> Wine has/had pdb partial support
> http://www.winehq.com/News/1999-49.html
>
> http://www.tbcnet.com/~clive/vcomwinp.html
> has a dumppe that understands codeview
>
> http://www.rdbooks.com/store/products/rd2364.htm is an old book -
maybe
> there is a newer version with CV4 info?
>
> http://www.wotsit.org/
> is a useful site on file formats - nothing there, but if you ask,
maybe
> they know where to find it.
>
> Codeview is also known as CV4 - a earch on that might help.
> MSDN spat out this:
> http://support.microsoft.com/support/kb/articles/Q194/9/21.ASP
> which has some partial info on the Codeview format.
>
> http://www.jorgon.freeserve.co.uk/GobugHelp/Symbolic.htm
> isn't really helpful, butmay be of interest
>
> Lastly, MSDN CD roms do have the Specification (CV5.0 Symbolic Debug
> Information) But I'm afraid to open it :]. Perhaps someone you know
can
> create a clean room spec for you.
>
> Rob
>
> ===
> ----- Original Message -----
> From: "Robert Collins" <robert.collins@itdomain.com.au>
> To: "Corinna Vinschen" <cygwin@cygwin.com>
> Sent: Wednesday, November 21, 2001 8:46 PM
> Subject: Re: gdb trouble
>
>
> > Some related articles:
> >
> > http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
> > /html/msdn_peeringpe.asp
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
> > bghelp_0l0n.asp?frame=true
> >
> > To me it looks like there are 2 options.
> > 1) add the user of the symbol handling library to gdb. That should
> allow
> > pdb use.
> > 2) Using the symbol handling library, and (say) VC++, generate test
> > exe's with .pdb and reverse engineer the format. Once done, use the
> > resulting library in gdb.
> >
> > Rob
> >
> >
> > ===
> > ----- Original Message -----
> > From: "Corinna Vinschen" <cygwin@cygwin.com>
> > To: "cygwin" <cygwin@cygwin.com>
> > Sent: Wednesday, November 21, 2001 8:29 PM
> > Subject: Re: gdb trouble
> >
> >
> > > On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > > > I  had  been using  softice  debugger  on windows  which  is
from
> > > > mega(  and  it understands pdb  format)  and  how   do they know
> > the
> > > > format?
> > > > I  think  it  would  be documented.
> > >
> > > Sure.  Somewhere.  Under NDA, I assume.
> > >
> > > Corinna
> > >
> > > --
> > > Corinna Vinschen                  Please, send mails regarding
> Cygwin
> > to
> > > Cygwin Developer
> > mailto:cygwin@cygwin.com
> > > Red Hat, Inc.
> > >
> > > --
> > > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > > Bug reporting:         http://cygwin.com/bugs.html
> > > Documentation:         http://cygwin.com/docs.html
> > > FAQ:                   http://cygwin.com/faq/
> > >
> > >
> >
> >
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting:         http://cygwin.com/bugs.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> >
> >
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Robert Collins]

Found it.

http://www.pearsonptg.com/book_detail/0,3771,0201721872,00.html

claims to document the pdb format.

Rob
===
----- Original Message -----
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Robert Collins" <robert.collins@itdomain.com.au>; "Corinna
Vinschen" <cygwin@cygwin.com>
Sent: Wednesday, November 21, 2001 9:42 PM
Subject: Re: gdb trouble


> And more (last one I think)
>
> Watcomm apparent support Codeview in their debug formats - and they
are
> open sourcing watcomm C/C++ - see http://www.openwatcom.org/
>
> Rob
> ===
> ----- Original Message -----
> From: "Robert Collins" <robert.collins@itdomain.com.au>
> To: "Robert Collins" <robert.collins@itdomain.com.au>; "Corinna
> Vinschen" <cygwin@cygwin.com>
> Sent: Wednesday, November 21, 2001 9:36 PM
> Subject: Re: gdb trouble
>
>
> > And some more that caught my eye:
> >
>
http://www.microsoft.com/msj/defaultframe.asp?page=/msj/0399/hood/hood03
> > 99.htm&nav=/msj/0399/newnav.htm
> > Is an article about .dbg file formats - not written my MS, and
> includdes
> > references to pdb.
> > It also has a handy file cvinfo.h which is the header required to
> > manipulate codeview 4 data.
> >
> > MSDN returns a hit on COFFTOCV.C which does what it says.
> >
> > http://www.winehq.com/hypermail/wine-patches/2001/08/0106.html
> > based on the info from the above header!
> >
> > http://support.microsoft.com/support/kb/articles/q121/3/66.asp
> >
> > These folk appear to be able to generate Codeview data (which is
what
> is
> > in pdb files).
> > http://www.digitalmars.com/faq.html
> > and http://www.digitalmars.com/bibliography.html (see CV4)
> >
> > Wine has/had pdb partial support
> > http://www.winehq.com/News/1999-49.html
> >
> > http://www.tbcnet.com/~clive/vcomwinp.html
> > has a dumppe that understands codeview
> >
> > http://www.rdbooks.com/store/products/rd2364.htm is an old book -
> maybe
> > there is a newer version with CV4 info?
> >
> > http://www.wotsit.org/
> > is a useful site on file formats - nothing there, but if you ask,
> maybe
> > they know where to find it.
> >
> > Codeview is also known as CV4 - a earch on that might help.
> > MSDN spat out this:
> > http://support.microsoft.com/support/kb/articles/Q194/9/21.ASP
> > which has some partial info on the Codeview format.
> >
> > http://www.jorgon.freeserve.co.uk/GobugHelp/Symbolic.htm
> > isn't really helpful, butmay be of interest
> >
> > Lastly, MSDN CD roms do have the Specification (CV5.0 Symbolic Debug
> > Information) But I'm afraid to open it :]. Perhaps someone you know
> can
> > create a clean room spec for you.
> >
> > Rob
> >
> > ===
> > ----- Original Message -----
> > From: "Robert Collins" <robert.collins@itdomain.com.au>
> > To: "Corinna Vinschen" <cygwin@cygwin.com>
> > Sent: Wednesday, November 21, 2001 8:46 PM
> > Subject: Re: gdb trouble
> >
> >
> > > Some related articles:
> > >
> > > http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
> > >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
> > > /html/msdn_peeringpe.asp
> > >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
> > > bghelp_0l0n.asp?frame=true
> > >
> > > To me it looks like there are 2 options.
> > > 1) add the user of the symbol handling library to gdb. That should
> > allow
> > > pdb use.
> > > 2) Using the symbol handling library, and (say) VC++, generate
test
> > > exe's with .pdb and reverse engineer the format. Once done, use
the
> > > resulting library in gdb.
> > >
> > > Rob
> > >
> > >
> > > ===
> > > ----- Original Message -----
> > > From: "Corinna Vinschen" <cygwin@cygwin.com>
> > > To: "cygwin" <cygwin@cygwin.com>
> > > Sent: Wednesday, November 21, 2001 8:29 PM
> > > Subject: Re: gdb trouble
> > >
> > >
> > > > On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > > > > I  had  been using  softice  debugger  on windows  which  is
> from
> > > > > mega(  and  it understands pdb  format)  and  how   do they
know
> > > the
> > > > > format?
> > > > > I  think  it  would  be documented.
> > > >
> > > > Sure.  Somewhere.  Under NDA, I assume.
> > > >
> > > > Corinna
> > > >
> > > > --
> > > > Corinna Vinschen                  Please, send mails regarding
> > Cygwin
> > > to
> > > > Cygwin Developer
> > > mailto:cygwin@cygwin.com
> > > > Red Hat, Inc.
> > > >
> > > > --
> > > > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > > > Bug reporting:         http://cygwin.com/bugs.html
> > > > Documentation:         http://cygwin.com/docs.html
> > > > FAQ:                   http://cygwin.com/faq/
> > > >
> > > >
> > >
> > >
> > > --
> > > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > > Bug reporting:         http://cygwin.com/bugs.html
> > > Documentation:         http://cygwin.com/docs.html
> > > FAQ:                   http://cygwin.com/faq/
> > >
> > >
> >
> >
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Robert Collins]

Found it.

http://www.pearsonptg.com/book_detail/0,3771,0201721872,00.html

claims to document the pdb format.

Rob
===
----- Original Message -----
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Robert Collins" <robert.collins@itdomain.com.au>; "Corinna
Vinschen" <cygwin@cygwin.com>
Sent: Wednesday, November 21, 2001 9:42 PM
Subject: Re: gdb trouble


> And more (last one I think)
>
> Watcomm apparent support Codeview in their debug formats - and they
are
> open sourcing watcomm C/C++ - see http://www.openwatcom.org/
>
> Rob
> ===
> ----- Original Message -----
> From: "Robert Collins" <robert.collins@itdomain.com.au>
> To: "Robert Collins" <robert.collins@itdomain.com.au>; "Corinna
> Vinschen" <cygwin@cygwin.com>
> Sent: Wednesday, November 21, 2001 9:36 PM
> Subject: Re: gdb trouble
>
>
> > And some more that caught my eye:
> >
>
http://www.microsoft.com/msj/defaultframe.asp?page=/msj/0399/hood/hood03
> > 99.htm&nav=/msj/0399/newnav.htm
> > Is an article about .dbg file formats - not written my MS, and
> includdes
> > references to pdb.
> > It also has a handy file cvinfo.h which is the header required to
> > manipulate codeview 4 data.
> >
> > MSDN returns a hit on COFFTOCV.C which does what it says.
> >
> > http://www.winehq.com/hypermail/wine-patches/2001/08/0106.html
> > based on the info from the above header!
> >
> > http://support.microsoft.com/support/kb/articles/q121/3/66.asp
> >
> > These folk appear to be able to generate Codeview data (which is
what
> is
> > in pdb files).
> > http://www.digitalmars.com/faq.html
> > and http://www.digitalmars.com/bibliography.html (see CV4)
> >
> > Wine has/had pdb partial support
> > http://www.winehq.com/News/1999-49.html
> >
> > http://www.tbcnet.com/~clive/vcomwinp.html
> > has a dumppe that understands codeview
> >
> > http://www.rdbooks.com/store/products/rd2364.htm is an old book -
> maybe
> > there is a newer version with CV4 info?
> >
> > http://www.wotsit.org/
> > is a useful site on file formats - nothing there, but if you ask,
> maybe
> > they know where to find it.
> >
> > Codeview is also known as CV4 - a earch on that might help.
> > MSDN spat out this:
> > http://support.microsoft.com/support/kb/articles/Q194/9/21.ASP
> > which has some partial info on the Codeview format.
> >
> > http://www.jorgon.freeserve.co.uk/GobugHelp/Symbolic.htm
> > isn't really helpful, butmay be of interest
> >
> > Lastly, MSDN CD roms do have the Specification (CV5.0 Symbolic Debug
> > Information) But I'm afraid to open it :]. Perhaps someone you know
> can
> > create a clean room spec for you.
> >
> > Rob
> >
> > ===
> > ----- Original Message -----
> > From: "Robert Collins" <robert.collins@itdomain.com.au>
> > To: "Corinna Vinschen" <cygwin@cygwin.com>
> > Sent: Wednesday, November 21, 2001 8:46 PM
> > Subject: Re: gdb trouble
> >
> >
> > > Some related articles:
> > >
> > > http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
> > >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
> > > /html/msdn_peeringpe.asp
> > >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
> > > bghelp_0l0n.asp?frame=true
> > >
> > > To me it looks like there are 2 options.
> > > 1) add the user of the symbol handling library to gdb. That should
> > allow
> > > pdb use.
> > > 2) Using the symbol handling library, and (say) VC++, generate
test
> > > exe's with .pdb and reverse engineer the format. Once done, use
the
> > > resulting library in gdb.
> > >
> > > Rob
> > >
> > >
> > > ===
> > > ----- Original Message -----
> > > From: "Corinna Vinschen" <cygwin@cygwin.com>
> > > To: "cygwin" <cygwin@cygwin.com>
> > > Sent: Wednesday, November 21, 2001 8:29 PM
> > > Subject: Re: gdb trouble
> > >
> > >
> > > > On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > > > > I  had  been using  softice  debugger  on windows  which  is
> from
> > > > > mega(  and  it understands pdb  format)  and  how   do they
know
> > > the
> > > > > format?
> > > > > I  think  it  would  be documented.
> > > >
> > > > Sure.  Somewhere.  Under NDA, I assume.
> > > >
> > > > Corinna
> > > >
> > > > --
> > > > Corinna Vinschen                  Please, send mails regarding
> > Cygwin
> > > to
> > > > Cygwin Developer
> > > mailto:cygwin@cygwin.com
> > > > Red Hat, Inc.
> > > >
> > > > --
> > > > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > > > Bug reporting:         http://cygwin.com/bugs.html
> > > > Documentation:         http://cygwin.com/docs.html
> > > > FAQ:                   http://cygwin.com/faq/
> > > >
> > > >
> > >
> > >
> > > --
> > > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > > Bug reporting:         http://cygwin.com/bugs.html
> > > Documentation:         http://cygwin.com/docs.html
> > > FAQ:                   http://cygwin.com/faq/
> > >
> > >
> >
> >
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Robert Collins]

And more (last one I think)

Watcomm apparent support Codeview in their debug formats - and they are
open sourcing watcomm C/C++ - see http://www.openwatcom.org/

Rob
===
----- Original Message -----
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Robert Collins" <robert.collins@itdomain.com.au>; "Corinna
Vinschen" <cygwin@cygwin.com>
Sent: Wednesday, November 21, 2001 9:36 PM
Subject: Re: gdb trouble


> And some more that caught my eye:
>
http://www.microsoft.com/msj/defaultframe.asp?page=/msj/0399/hood/hood03
> 99.htm&nav=/msj/0399/newnav.htm
> Is an article about .dbg file formats - not written my MS, and
includdes
> references to pdb.
> It also has a handy file cvinfo.h which is the header required to
> manipulate codeview 4 data.
>
> MSDN returns a hit on COFFTOCV.C which does what it says.
>
> http://www.winehq.com/hypermail/wine-patches/2001/08/0106.html
> based on the info from the above header!
>
> http://support.microsoft.com/support/kb/articles/q121/3/66.asp
>
> These folk appear to be able to generate Codeview data (which is what
is
> in pdb files).
> http://www.digitalmars.com/faq.html
> and http://www.digitalmars.com/bibliography.html (see CV4)
>
> Wine has/had pdb partial support
> http://www.winehq.com/News/1999-49.html
>
> http://www.tbcnet.com/~clive/vcomwinp.html
> has a dumppe that understands codeview
>
> http://www.rdbooks.com/store/products/rd2364.htm is an old book -
maybe
> there is a newer version with CV4 info?
>
> http://www.wotsit.org/
> is a useful site on file formats - nothing there, but if you ask,
maybe
> they know where to find it.
>
> Codeview is also known as CV4 - a earch on that might help.
> MSDN spat out this:
> http://support.microsoft.com/support/kb/articles/Q194/9/21.ASP
> which has some partial info on the Codeview format.
>
> http://www.jorgon.freeserve.co.uk/GobugHelp/Symbolic.htm
> isn't really helpful, butmay be of interest
>
> Lastly, MSDN CD roms do have the Specification (CV5.0 Symbolic Debug
> Information) But I'm afraid to open it :]. Perhaps someone you know
can
> create a clean room spec for you.
>
> Rob
>
> ===
> ----- Original Message -----
> From: "Robert Collins" <robert.collins@itdomain.com.au>
> To: "Corinna Vinschen" <cygwin@cygwin.com>
> Sent: Wednesday, November 21, 2001 8:46 PM
> Subject: Re: gdb trouble
>
>
> > Some related articles:
> >
> > http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
> > /html/msdn_peeringpe.asp
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
> > bghelp_0l0n.asp?frame=true
> >
> > To me it looks like there are 2 options.
> > 1) add the user of the symbol handling library to gdb. That should
> allow
> > pdb use.
> > 2) Using the symbol handling library, and (say) VC++, generate test
> > exe's with .pdb and reverse engineer the format. Once done, use the
> > resulting library in gdb.
> >
> > Rob
> >
> >
> > ===
> > ----- Original Message -----
> > From: "Corinna Vinschen" <cygwin@cygwin.com>
> > To: "cygwin" <cygwin@cygwin.com>
> > Sent: Wednesday, November 21, 2001 8:29 PM
> > Subject: Re: gdb trouble
> >
> >
> > > On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > > > I  had  been using  softice  debugger  on windows  which  is
from
> > > > mega(  and  it understands pdb  format)  and  how   do they know
> > the
> > > > format?
> > > > I  think  it  would  be documented.
> > >
> > > Sure.  Somewhere.  Under NDA, I assume.
> > >
> > > Corinna
> > >
> > > --
> > > Corinna Vinschen                  Please, send mails regarding
> Cygwin
> > to
> > > Cygwin Developer
> > mailto:cygwin@cygwin.com
> > > Red Hat, Inc.
> > >
> > > --
> > > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > > Bug reporting:         http://cygwin.com/bugs.html
> > > Documentation:         http://cygwin.com/docs.html
> > > FAQ:                   http://cygwin.com/faq/
> > >
> > >
> >
> >
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting:         http://cygwin.com/bugs.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> >
> >
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Robert Collins]

And some more that caught my eye:
http://www.microsoft.com/msj/defaultframe.asp?page=/msj/0399/hood/hood03
99.htm&nav=/msj/0399/newnav.htm
Is an article about .dbg file formats - not written my MS, and includdes
references to pdb.
It also has a handy file cvinfo.h which is the header required to
manipulate codeview 4 data.

MSDN returns a hit on COFFTOCV.C which does what it says.

http://www.winehq.com/hypermail/wine-patches/2001/08/0106.html
based on the info from the above header!

http://support.microsoft.com/support/kb/articles/q121/3/66.asp

These folk appear to be able to generate Codeview data (which is what is
in pdb files).
http://www.digitalmars.com/faq.html
and http://www.digitalmars.com/bibliography.html (see CV4)

Wine has/had pdb partial support
http://www.winehq.com/News/1999-49.html

http://www.tbcnet.com/~clive/vcomwinp.html
has a dumppe that understands codeview

http://www.rdbooks.com/store/products/rd2364.htm is an old book - maybe
there is a newer version with CV4 info?

http://www.wotsit.org/
is a useful site on file formats - nothing there, but if you ask, maybe
they know where to find it.

Codeview is also known as CV4 - a earch on that might help.
MSDN spat out this:
http://support.microsoft.com/support/kb/articles/Q194/9/21.ASP
which has some partial info on the Codeview format.

http://www.jorgon.freeserve.co.uk/GobugHelp/Symbolic.htm
isn't really helpful, butmay be of interest

Lastly, MSDN CD roms do have the Specification (CV5.0 Symbolic Debug
Information) But I'm afraid to open it :]. Perhaps someone you know can
create a clean room spec for you.

Rob

===
----- Original Message -----
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Corinna Vinschen" <cygwin@cygwin.com>
Sent: Wednesday, November 21, 2001 8:46 PM
Subject: Re: gdb trouble


> Some related articles:
>
> http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
> /html/msdn_peeringpe.asp
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
> bghelp_0l0n.asp?frame=true
>
> To me it looks like there are 2 options.
> 1) add the user of the symbol handling library to gdb. That should
allow
> pdb use.
> 2) Using the symbol handling library, and (say) VC++, generate test
> exe's with .pdb and reverse engineer the format. Once done, use the
> resulting library in gdb.
>
> Rob
>
>
> ===
> ----- Original Message -----
> From: "Corinna Vinschen" <cygwin@cygwin.com>
> To: "cygwin" <cygwin@cygwin.com>
> Sent: Wednesday, November 21, 2001 8:29 PM
> Subject: Re: gdb trouble
>
>
> > On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > > I  had  been using  softice  debugger  on windows  which  is from
> > > mega(  and  it understands pdb  format)  and  how   do they know
> the
> > > format?
> > > I  think  it  would  be documented.
> >
> > Sure.  Somewhere.  Under NDA, I assume.
> >
> > Corinna
> >
> > --
> > Corinna Vinschen                  Please, send mails regarding
Cygwin
> to
> > Cygwin Developer
> mailto:cygwin@cygwin.com
> > Red Hat, Inc.
> >
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting:         http://cygwin.com/bugs.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> >
> >
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Robert Collins]

Some related articles:

http://support.microsoft.com/support/kb/articles/Q182/0/43.ASP
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen
/html/msdn_peeringpe.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/d
bghelp_0l0n.asp?frame=true

To me it looks like there are 2 options.
1) add the user of the symbol handling library to gdb. That should allow
pdb use.
2) Using the symbol handling library, and (say) VC++, generate test
exe's with .pdb and reverse engineer the format. Once done, use the
resulting library in gdb.

Rob


===
----- Original Message -----
From: "Corinna Vinschen" <cygwin@cygwin.com>
To: "cygwin" <cygwin@cygwin.com>
Sent: Wednesday, November 21, 2001 8:29 PM
Subject: Re: gdb trouble


> On Wed, Nov 21, 2001 at 10:14:43AM +0530, vipin aravind wrote:
> > I  had  been using  softice  debugger  on windows  which  is from
> > mega(  and  it understands pdb  format)  and  how   do they know
the
> > format?
> > I  think  it  would  be documented.
>
> Sure.  Somewhere.  Under NDA, I assume.
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin
to
> Cygwin Developer
mailto:cygwin@cygwin.com
> Red Hat, Inc.
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[vipin aravind]

[-- Attachment #1.1: Type: text/plain, Size: 759 bytes --]

oops  sorry  the  executeable  was  created  as a.exe and gdb a  worked
How   do  I get  the prefix  same as the source file.
Is it possible  to debug  vc++ generated exe's?
vipin
  ----- Original Message ----- 
  From: vipin aravind 
  To: cygwin@cygwin.com 
  Sent: Tuesday, November 20, 2001 1:49 PM
  Subject: gdb trouble


  hi,
  I have done
  1)gcc -g  test.c
  2)  gdb 
  3)   from the  "run"  menu I choose  the executeable  I get  the following error-message box.

   
   
  ---------------------------
  Error
  ---------------------------
  Error loading "/home/Administrator/test":
   not in executable format: File format not recognized

  ---------------------------
  OK   
  ---------------------------

  vipin

[-- Attachment #1.2: Type: text/html, Size: 2396 bytes --]

[-- Attachment #2: InterScan_Disclaimer.txt --]
[-- Type: text/plain, Size: 856 bytes --]

-------------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------


[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[Corinna Vinschen]

On Tue, Nov 20, 2001 at 01:52:20PM +0530, vipin aravind wrote:
> oops  sorry  the  executeable  was  created  as a.exe and gdb a  worked
> How   do  I get  the prefix  same as the source file.

gcc -o outputfilename ...

> Is it possible  to debug  vc++ generated exe's?

Not really.  Microsoft is using a proprietary debug format (.pch files).
You would be stuck with assembler debugging.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: gdb trouble

[David Starks-Browning]

On Tuesday 20 Nov 01, vipin aravind writes:
> oops  sorry  the  executeable  was  created  as a.exe and gdb a  worked
> How   do  I get  the prefix  same as the source file.

"man gcc" or "info gcc"

will tell you:

	gcc -o test test.c

does what you are asking.  BUT DON'T DO THAT!!!

Don't create executables called "test" or "test.exe".  Unix (and thus
Cygwin) has its own version of "test", and you will have trouble
getting the right "test" invoked.

Choose some other name instead:

	gcc -o myprog test.c
or	gcc -o a test.c

Regards,
David


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

GDB trouble

[Brad Scott]

I've searched the archives and online help, and I can't find an answer to
my problem. Gcc and bash seem to work fine, but gdb keeps crashing my
system. It will run for a short while, but after I've entered 3 or 4
commands, it freezes up. If I try to shut it down from windows, the whole
computer freezes, to the extent where I can't even re-boot it without
turning it off and on. I'm using windows95, and I've tried running gdb from
dos, bash and tclsh, and its the same with all of them. I installed tmp and
bin directories as instucted, and here's what I added to autoexec.bat:
SET PATH=%PATH%;C:\gnuwin32\b18\H-i386-cygwin32\bin;C:\gnuwin32\b18\tcl\bin
SET GCC_EXEC_PREFIX=C:\gnuwin32\b18\H-i386-cygwin32\lib\gcc-lib\
SET TCL_LIBRARY=C:/gnuwin32/b18/tcl/lib/tcl7.6
SET GDBTK_LIBRARY=C:/gnuwin32/b18/share/gdbtcl
SET LIBRARY_PATH=C:\gnuwin32\b18\H-i386-cygwin32\lib;
I tried re-doing the installation from the download file, but that didn't
do anything.
I'm pretty clueless with unix, so I'm hoping thats what my problem is.
Thanks
Brad
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".