cdt-dev

[cdt-dev] RC1

dschaefer@xxxxxxx (Doug Schaefer) — Wed, 22 May 2013 13:32:23 GMT

With the long weekend up here in Canada, I forgot to grab a build for RC1. So I did that this morning. It is here and hooked into our composite milestones repo:

http://download.eclipse.org/tools/cdt/builds/kepler/milestones/rc1

Re: [cdt-dev] Why is .gdbinit specified explicitly?

eclipse.sprigogin@xxxxxxx (Sergey Prigogin) — Tue, 21 May 2013 02:35:51 GMT

Oh, I see. I somehow misinterpreted "command file" as "command line". Thanks for pointing it out.

-sergey

On Mon, May 20, 2013 at 6:37 PM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:

I'm not sure what you mean by GDB command-line.  We launch GDB with 'gdb --nx'.  We then specify the gdbinit file to be used, by using an MI command.  '.gdbinit' is used because it is specified in the launch configuration.

The idea was to allow people extending DSF-GDB to easily override any configuration that was being done by default.


Best regards,

Marc


----- Original Message -----
From: Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx>
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Sent: 20-05-2013 16:48
Subject: Re: [cdt-dev] Why is .gdbinit specified explicitly?
A desire to support different init files in different configurations doesn't seem to be relevant to the choice of the default gdb command line.

On Mon, May 20, 2013 at 1:15 PM, Eugene Ostroukhov <eostroukhov@xxxxxxxxx> wrote:

I assume it's for scenarios like having different init files in different debug configurations.

On Mon, May 20, 2013 at 12:14 PM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

This only makes it more mysterious. Why pass .gdbinit after --nx on the command line? What purpose does it achieve?

-sergey

On Mon, May 20, 2013 at 12:02 PM, Eugene Ostroukhov <eostroukhov@xxxxxxxxx> wrote:

There's this comment in GDBBackend:197 (my line number might be slightly off), don't know if you've seen it:

// Don't read the gdbinit file here.Â It is read explicitly in

// the LaunchSequence to make it easier to customize.

gdbCommandLine.append(" --nx"); //$NON-NLS-1$

On Mon, May 20, 2013 at 11:20 AM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

Does anybody know why DSF GDB default for GDB command line is ".gdbint"? Doesn't GDB load .gdbinit anyway, even when it is not specified on the command line?

-sergeyÂ

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Re: [cdt-dev] Why is .gdbinit specified explicitly?

marc.khouzam@xxxxxxx (Marc Khouzam) — Tue, 21 May 2013 01:37:18 GMT

I'm not sure what you mean by GDB command-line.  We launch GDB with 'gdb --nx'.  We then specify the gdbinit file to be used, by using an MI command.  '.gdbinit' is used because it is specified in the launch configuration.

The idea was to allow people extending DSF-GDB to easily override any configuration that was being done by default.


Best regards,

Marc


----- Original Message -----
From: Sergey Prigogin 
To: "CDT General developers list." 
Sent: 20-05-2013 16:48
Subject: Re: [cdt-dev] Why is .gdbinit specified explicitly?

A desire to support different init files in different configurations doesn't seem to be relevant to the choice of the default gdb command line.

On Mon, May 20, 2013 at 1:15 PM, Eugene Ostroukhov <eostroukhov@xxxxxxxxx> wrote:

I assume it's for scenarios like having different init files in different debug configurations.

On Mon, May 20, 2013 at 12:14 PM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

This only makes it more mysterious. Why pass .gdbinit after --nx on the command line? What purpose does it achieve?

-sergey

On Mon, May 20, 2013 at 12:02 PM, Eugene Ostroukhov <eostroukhov@xxxxxxxxx> wrote:

There's this comment in GDBBackend:197 (my line number might be slightly off), don't know if you've seen it:

// Don't read the gdbinit file here. It is read explicitly in

// the LaunchSequence to make it easier to customize.

gdbCommandLine.append(" --nx"); //$NON-NLS-1$

On Mon, May 20, 2013 at 11:20 AM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

Does anybody know why DSF GDB default for GDB command line is ".gdbint"? Doesn't GDB load .gdbinit anyway, even when it is not specified on the command line?

-sergey

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Re: [cdt-dev] Why is .gdbinit specified explicitly?

eclipse.sprigogin@xxxxxxx (Sergey Prigogin) — Mon, 20 May 2013 20:47:52 GMT

A desire to support different init files in different configurations doesn't seem to be relevant to the choice of the default gdb command line.

On Mon, May 20, 2013 at 1:15 PM, Eugene Ostroukhov <eostroukhov@xxxxxxxxx> wrote:

I assume it's for scenarios like having different init files in different debug configurations.

On Mon, May 20, 2013 at 12:14 PM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

This only makes it more mysterious. Why pass .gdbinit after --nx on the command line? What purpose does it achieve?

-sergey

On Mon, May 20, 2013 at 12:02 PM, Eugene Ostroukhov <eostroukhov@xxxxxxxxx> wrote:

There's this comment in GDBBackend:197 (my line number might be slightly off), don't know if you've seen it:

// Don't read the gdbinit file here.Â It is read explicitly in

// the LaunchSequence to make it easier to customize.

gdbCommandLine.append(" --nx"); //$NON-NLS-1$

On Mon, May 20, 2013 at 11:20 AM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

Does anybody know why DSF GDB default for GDB command line is ".gdbint"? Doesn't GDB load .gdbinit anyway, even when it is not specified on the command line?

-sergeyÂ

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Re: [cdt-dev] Why is .gdbinit specified explicitly?

eostroukhov@xxxxxxx (Eugene Ostroukhov) — Mon, 20 May 2013 20:15:50 GMT

I assume it's for scenarios like having different init files in different debug configurations.

On Mon, May 20, 2013 at 12:14 PM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

This only makes it more mysterious. Why pass .gdbinit after --nx on the command line? What purpose does it achieve?

-sergey

On Mon, May 20, 2013 at 12:02 PM, Eugene Ostroukhov <eostroukhov@xxxxxxxxx> wrote:

There's this comment in GDBBackend:197 (my line number might be slightly off), don't know if you've seen it:

// Don't read the gdbinit file here.Â It is read explicitly in

// the LaunchSequence to make it easier to customize.

gdbCommandLine.append(" --nx"); //$NON-NLS-1$

On Mon, May 20, 2013 at 11:20 AM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

Does anybody know why DSF GDB default for GDB command line is ".gdbint"? Doesn't GDB load .gdbinit anyway, even when it is not specified on the command line?

-sergeyÂ

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Re: [cdt-dev] Why is .gdbinit specified explicitly?

eclipse.sprigogin@xxxxxxx (Sergey Prigogin) — Mon, 20 May 2013 19:14:22 GMT

This only makes it more mysterious. Why pass .gdbinit after --nx on the command line? What purpose does it achieve?

-sergey

On Mon, May 20, 2013 at 12:02 PM, Eugene Ostroukhov <eostroukhov@xxxxxxxxx> wrote:

There's this comment in GDBBackend:197 (my line number might be slightly off), don't know if you've seen it:

// Don't read the gdbinit file here.Â It is read explicitly in

// the LaunchSequence to make it easier to customize.

gdbCommandLine.append(" --nx"); //$NON-NLS-1$

On Mon, May 20, 2013 at 11:20 AM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

Does anybody know why DSF GDB default for GDB command line is ".gdbint"? Doesn't GDB load .gdbinit anyway, even when it is not specified on the command line?

-sergeyÂ

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Re: [cdt-dev] Why is .gdbinit specified explicitly?

eostroukhov@xxxxxxx (Eugene Ostroukhov) — Mon, 20 May 2013 19:02:53 GMT

There's this comment in GDBBackend:197 (my line number might be slightly off), don't know if you've seen it:

// Don't read the gdbinit file here.Â It is read explicitly in

// the LaunchSequence to make it easier to customize.

gdbCommandLine.append(" --nx"); //$NON-NLS-1$

On Mon, May 20, 2013 at 11:20 AM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

Does anybody know why DSF GDB default for GDB command line is ".gdbint"? Doesn't GDB load .gdbinit anyway, even when it is not specified on the command line?

-sergeyÂ

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

[cdt-dev] Why is .gdbinit specified explicitly?

eclipse.sprigogin@xxxxxxx (Sergey Prigogin) — Mon, 20 May 2013 18:20:42 GMT

Does anybody know why DSF GDB default for GDB command line is ".gdbint"? Doesn't GDB load .gdbinit anyway, even when it is not specified on the command line?

-sergeyÂ

Re: [cdt-dev] "Ctrl+." no longer goes to next error

eclipse.sprigogin@xxxxxxx (Sergey Prigogin) — Sun, 19 May 2013 17:03:18 GMT

I've reopenedÂhttps://bugs.eclipse.org/bugs/show_bug.cgi?id=368221.

-sergey

On Sun, May 19, 2013 at 9:47 AM, Axel MÃller <axel.carl.mueller@xxxxxxxxx> wrote:

Hi,

I guess this was caused by my patchÂhttps://bugs.eclipse.org/bugs/show_bug.cgi?id=368221Âthat addedÂPreference options for Codan annotation markers. At the moment the markers are excluded from the next/previous navigation. It would be easy to reenable it. Please open a bug and I submit a patch.

ÂAxel

2013/5/16 Nathan Ridge <zeratul976@xxxxxxxxxxx>

> Could it be that it is just disabled? Look in the workbench's toolbar for the "Next Annotation" button and check whether "Error" and "Warning" is enabled.

The button is enabled, and "Error" and "Warning" are enabled, but
pressing the button or using the shortcut does nothing.

I tried enabling all of the other annotation types, still nothing.

It's as if the type of semantic error annotations changed from
"Error" to some other category that's not on the list.

Nate
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

--
Dr. Axel MÃller
Lorbeerweg 8
76149 Karlsruhe

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Re: [cdt-dev] "Ctrl+." no longer goes to next error

axel.carl.mueller@xxxxxxx (Axel Müller) — Sun, 19 May 2013 16:47:42 GMT

Hi,

I guess this was caused by my patch https://bugs.eclipse.org/bugs/show_bug.cgi?id=368221 that added Preference options for Codan annotation markers. At the moment the markers are excluded from the next/previous navigation. It would be easy to reenable it. Please open a bug and I submit a patch.

Axel

2013/5/16 Nathan Ridge <zeratul976@xxxxxxxxxxx>

> Could it be that it is just disabled? Look in the workbench's toolbar for the "Next Annotation" button and check whether "Error" and "Warning" is enabled.

The button is enabled, and "Error" and "Warning" are enabled, but
pressing the button or using the shortcut does nothing.

I tried enabling all of the other annotation types, still nothing.

It's as if the type of semantic error annotations changed from
"Error" to some other category that's not on the list.

Nate
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

--
Dr. Axel Müller
Lorbeerweg 8
76149 Karlsruhe