bug#13057: BUG: gdb main window corrupt

bug#13057: BUG: gdb main window corrupt

[Alan Boudreault]

I'm currently using emacs 24.2.1 and using it to debug a remote program 
via tramp. Everytime I execute a command, there is a *list* command 
automatically executed, which just spam my main window. Kind of annoying 
when I try to debug. Is there a workaround? (btw, I've also tried emacs 
24.3 but I can't load anymore a remote program in gdb with this version.)


Here's my gud buffer:
-----------*gud-mapserv*-----------------
(gdb) p mapserv
$1 = (mapservObj *) 0x60e6c0
(gdb) list mapserv.c:1     # <------ THIS IS AUTOMATICALLY CALLED AFTER 
EACH COMMAND I TYPE
1 
/******************************************************************************
2	 * $id: mapserv.c 9470 2009-10-16 16:09:31Z sdlime $
3	 *
4	 * Project:  MapServer
5	 * Purpose:  MapServer CGI mainline.
6	 * Author:   Steve Lime and the MapServer team.
7	 *
8	 
******************************************************************************
9	 * Copyright (c) 1996-2005 Regents of the University of Minnesota.
10	 *


Thanks,
Alan

bug#13057: BUG: gdb main window corrupt

[Eli Zaretskii]

> Date: Sun, 02 Dec 2012 09:14:47 -0500
> From: Alan Boudreault <boudreault.alan@gmail.com>
> 
> I'm currently using emacs 24.2.1 and using it to debug a remote program 
> via tramp. Everytime I execute a command, there is a *list* command 
> automatically executed, which just spam my main window. Kind of annoying 
> when I try to debug. Is there a workaround? (btw, I've also tried emacs 
> 24.3 but I can't load anymore a remote program in gdb with this version.)
> 
> 
> Here's my gud buffer:
> -----------*gud-mapserv*-----------------
> (gdb) p mapserv
> $1 = (mapservObj *) 0x60e6c0
> (gdb) list mapserv.c:1     # <------ THIS IS AUTOMATICALLY CALLED AFTER 
> EACH COMMAND I TYPE
> 1 
> /******************************************************************************
> 2	 * $id: mapserv.c 9470 2009-10-16 16:09:31Z sdlime $
> 3	 *
> 4	 * Project:  MapServer
> 5	 * Purpose:  MapServer CGI mainline.
> 6	 * Author:   Steve Lime and the MapServer team.
> 7	 *
> 8	 
> ******************************************************************************
> 9	 * Copyright (c) 1996-2005 Regents of the University of Minnesota.
> 10	 *

Thank you for your report.  Please use "M-x report-emacs-bug RET" to
send all the information that might be relevant to the bug.

Also, does this "list" command get sent for every program you try to
debug?  Does it get sent when debugging natively (i.e., not remotely)?

bug#13057: BUG: gdb main window corrupt

[Alan Boudreault]

Hi Eli,

I've tried 2 differents remote programs and got the same bug. However, I 
haven't seen the same behavior debugging remotely. Also, it seems to be 
only the first gdb process I run that has that behavior. If I open a 
first gdb process... I see the bug.... and If I open another gdb process 
there is no more list command executed and I can debug properly.

Alan

On 12-12-02 01:29 PM, Eli Zaretskii wrote:
>> Date: Sun, 02 Dec 2012 09:14:47 -0500
>> From: Alan Boudreault <boudreault.alan@gmail.com>
>>
>> I'm currently using emacs 24.2.1 and using it to debug a remote program
>> via tramp. Everytime I execute a command, there is a *list* command
>> automatically executed, which just spam my main window. Kind of annoying
>> when I try to debug. Is there a workaround? (btw, I've also tried emacs
>> 24.3 but I can't load anymore a remote program in gdb with this version.)
>>
>>
>> Here's my gud buffer:
>> -----------*gud-mapserv*-----------------
>> (gdb) p mapserv
>> $1 = (mapservObj *) 0x60e6c0
>> (gdb) list mapserv.c:1     # <------ THIS IS AUTOMATICALLY CALLED AFTER
>> EACH COMMAND I TYPE
>> 1
>> /******************************************************************************
>> 2	 * $id: mapserv.c 9470 2009-10-16 16:09:31Z sdlime $
>> 3	 *
>> 4	 * Project:  MapServer
>> 5	 * Purpose:  MapServer CGI mainline.
>> 6	 * Author:   Steve Lime and the MapServer team.
>> 7	 *
>> 8	
>> ******************************************************************************
>> 9	 * Copyright (c) 1996-2005 Regents of the University of Minnesota.
>> 10	 *
>
> Thank you for your report.  Please use "M-x report-emacs-bug RET" to
> send all the information that might be relevant to the bug.
>
> Also, does this "list" command get sent for every program you try to
> debug?  Does it get sent when debugging natively (i.e., not remotely)?
>

bug#13057: BUG: gdb main window corrupt

[Eli Zaretskii]

> Date: Tue, 04 Dec 2012 09:47:37 -0500
> From: Alan Boudreault <boudreault.alan@gmail.com>
> CC: 13057@debbugs.gnu.org
> 
> I've tried 2 differents remote programs and got the same bug. However, I 
> haven't seen the same behavior debugging remotely. Also, it seems to be 
> only the first gdb process I run that has that behavior. If I open a 
> first gdb process... I see the bug.... and If I open another gdb process 
> there is no more list command executed and I can debug properly.

This command comes from the function gdb-place-breakpoints (see
gdb-mi.el).  From cursory reading of that function, it looks like it
issues this command when it cannot glean the file name from what GDB
replies.  Maybe you could try upgrading to a newer GDB, because it
could be a GDB problem that triggers this command.

bug#13057: BUG: gdb main window corrupt

[Alan Boudreault]

Hi Eli,

I've upgraded to gdb 7.5-0gnu1~12.04 (from the GNU launchpad ppa for 
Ubuntu, for both local and remote machines) and I'm seeing the same issue.

Regards,
Alan

On 12-12-04 01:53 PM, Eli Zaretskii wrote:
>> Date: Tue, 04 Dec 2012 09:47:37 -0500
>> From: Alan Boudreault <boudreault.alan@gmail.com>
>> CC: 13057@debbugs.gnu.org
>>
>> I've tried 2 differents remote programs and got the same bug. However, I
>> haven't seen the same behavior debugging remotely. Also, it seems to be
>> only the first gdb process I run that has that behavior. If I open a
>> first gdb process... I see the bug.... and If I open another gdb process
>> there is no more list command executed and I can debug properly.
>
> This command comes from the function gdb-place-breakpoints (see
> gdb-mi.el).  From cursory reading of that function, it looks like it
> issues this command when it cannot glean the file name from what GDB
> replies.  Maybe you could try upgrading to a newer GDB, because it
> could be a GDB problem that triggers this command.
>

bug#13057: BUG: gdb main window corrupt

[Eli Zaretskii]

> Date: Tue, 04 Dec 2012 19:37:31 -0500
> From: Alan Boudreault <boudreault.alan@gmail.com>
> CC: 13057@debbugs.gnu.org
> 
> I've upgraded to gdb 7.5-0gnu1~12.04 (from the GNU launchpad ppa for 
> Ubuntu, for both local and remote machines) and I'm seeing the same issue.

Thanks.  Does the same happen in native debugging?  If so, can you
show a minimal program that could be used to reproduce the problem?

bug#13057: BUG: gdb main window corrupt

[Alan Boudreault]

Eli,

Did you get my private message about this bug? (no rush, just wondering).

Alan

On 12-12-04 10:49 PM, Eli Zaretskii wrote:
>> Date: Tue, 04 Dec 2012 19:37:31 -0500
>> From: Alan Boudreault <boudreault.alan@gmail.com>
>> CC: 13057@debbugs.gnu.org
>>
>> I've upgraded to gdb 7.5-0gnu1~12.04 (from the GNU launchpad ppa for
>> Ubuntu, for both local and remote machines) and I'm seeing the same issue.
>
> Thanks.  Does the same happen in native debugging?  If so, can you
> show a minimal program that could be used to reproduce the problem?
>

bug#13057: BUG: gdb main window corrupt

[Eli Zaretskii]

> Date: Tue, 18 Dec 2012 11:31:26 -0500
> From: Alan Boudreault <boudreault.alan@gmail.com>
> CC: 13057@debbugs.gnu.org
> 
> Eli,
> 
> Did you get my private message about this bug? (no rush, just wondering).

Yes, I did.  Didn't have time to do anything about it yet, though.

bug#13057: BUG: gdb main window corrupt

[Alan Boudreault]

Hi devs, if anyone is interested to take a look, I have a environment 
ready so you can reproduce the issue in a minute. Ping me privately for 
the info.

Thanks,
Alan

On 12-12-18 12:49 PM, Eli Zaretskii wrote:
>> Date: Tue, 18 Dec 2012 11:31:26 -0500
>> From: Alan Boudreault <boudreault.alan@gmail.com>
>> CC: 13057@debbugs.gnu.org
>>
>> Eli,
>>
>> Did you get my private message about this bug? (no rush, just wondering).
>
> Yes, I did.  Didn't have time to do anything about it yet, though.
>

bug#13057: BUG: gdb main window corrupt

[Alan Boudreault]

Any new investigation about this one? Or a hack/workaround available?

Best Regards,
Alan

On 12-12-18 12:49 PM, Eli Zaretskii wrote:
>> Date: Tue, 18 Dec 2012 11:31:26 -0500
>> From: Alan Boudreault <boudreault.alan@gmail.com>
>> CC: 13057@debbugs.gnu.org
>>
>> Eli,
>>
>> Did you get my private message about this bug? (no rush, just wondering).
>
> Yes, I did.  Didn't have time to do anything about it yet, though.
>

bug#13057: BUG: gdb main window corrupt

[Eli Zaretskii]

> Date: Mon, 28 Jan 2013 15:11:15 -0500
> From: Alan Boudreault <boudreault.alan@gmail.com>
> CC: 13057@debbugs.gnu.org
> 
> Any new investigation about this one?

Not from me, sorry.

> Or a hack/workaround available?

A workaround would be to use "M-x gud-gdb" instead.

bug#13057: BUG: gdb main window corrupt

[Alan Boudreault]

This workaround effectively works.

Thanks Eli!

Alan

On 13-01-29 01:47 AM, Eli Zaretskii wrote:
>> Date: Mon, 28 Jan 2013 15:11:15 -0500
>> From: Alan Boudreault <boudreault.alan@gmail.com>
>> CC: 13057@debbugs.gnu.org
>>
>> Any new investigation about this one?
>
> Not from me, sorry.
>
>> Or a hack/workaround available?
>
> A workaround would be to use "M-x gud-gdb" instead.
>

bug#13057: BUG: gdb main window corrupt

[Lars Ingebrigtsen]

Alan Boudreault <boudreault.alan@gmail.com> writes:

> I'm currently using emacs 24.2.1 and using it to debug a remote
> program via tramp. Everytime I execute a command, there is a *list*
> command automatically executed, which just spam my main window. Kind
> of annoying when I try to debug. Is there a workaround? (btw, I've
> also tried emacs 24.3 but I can't load anymore a remote program in gdb
> with this version.)

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

Are you still seeing this issue in recent versions of Emacs/gdb?  (When
not using gud-gdb.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#13057: BUG: gdb main window corrupt

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Are you still seeing this issue in recent versions of Emacs/gdb?  (When
> not using gud-gdb.)

More information was requested, but no response was given within a
month, so I'm closing this bug report.  If the problem still exists,
please respond to this email and we'll reopen the bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no