This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] print error message if (auto) disassembly failed


Agree with you.
I will post a patch for it.

Thanks,
Hui

On Fri, Apr 17, 2009 at 23:57, Joel Brobecker <brobecker@adacore.com> wrote:
>> In before, when the user step into the program that don't have line
>> message, ?they will lost the the help from debuger. ?They will not
>> know what will happen in next except a pc address.
>
> IMO, the vast majority of gdb users will not care, or even understand
> what the instruction means. Most of the time, the only reason I would
> personally land in code that doesn't have any debugging info is when
> attaching to a program, loading a core file, or pressing control-c.
> In such cases, the first thing I usually do is "break ...; continue".
>
> I have very very very occasionally done stepi's that got me inside
> such code, but in that case, I use a special user-defined command
> that does the stepi and then prints the instruction.
>
>> For now, this auto will auto output the asm code. ?I think it will
>> make user experience (special for new user) better.
>> And I think ?Joel's patch fix the bug.
>
> It's not just about the bug, actually - I wasn't suggesting that
> we change the default as a way to make it go away. Rather, I think
> that this default setting will be useful to only very few people,
> while at the same time creating the equivalent of noise for the
> rest of the population. This is why I maintain my suggestion of
> changing the default to "off".
>
> --
> Joel
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]