Re: "Getting Traces"
António Fernandes <[email protected]> Fri, 29 Mar 2013 20:17:55 +0000
| Newsgroups | gmane.comp.gnome.bugsquad |
|---|---|
| Message-ID | <CAJa6SmcfW_1uZY8ssfN+0QtosVYH2Tv1bLAP5CxN16uLWsiaww@mail.gmail.com> |
--===============5182808500417582255== Content-Type: multipart/alternative; boundary=f46d044286ca9dc55d04d915f8a4 --f46d044286ca9dc55d04d915f8a4 Content-Type: text/plain; charset=ISO-8859-1 So, I have some questions: 1- https://live.gnome.org/GettingTraces/Details#Obtaining_a_stack_trace_for_an_applet_using_just_GDB This was relevant in GNOME 2 days, but now that even Fallback mode is obsolete, applets are no longer widely used. I know that gnome-panel is still mantained and a bugzilla.gnome.org product, but is it worth keeping these instructions on this already long page? 2- With the introduction of a classic mode built on gnome-shell extensions, do we need instructions for gnome-shell extensions? 3- Current instructions ask for reporters to add the traces as an attachment. I've noticed that bugzilla recognizes such text files as binary files. Also, I've seen reports where traces shows up in the description, expandable in line, instead of being an ordinary attachment. Example: https://bugzilla.gnome.org/show_bug.cgi?id=594425 I don't know how to do that, but it looks like something we should instruct reporters to do instead. --f46d044286ca9dc55d04d915f8a4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>So, I have some questions:<br><br></div>1-<br><div><d= iv><div><a href=3D"https://live.gnome.org/GettingTraces/Details#Obtaining_a= _stack_trace_for_an_applet_using_just_GDB">https://live.gnome.org/GettingTr= aces/Details#Obtaining_a_stack_trace_for_an_applet_using_just_GDB</a><br> <br></div><div>This was relevant in GNOME 2 days, but now that even Fallbac= k mode is obsolete, applets are no longer widely used. I know that gnome-pa= nel is still mantained and a <a href=3D"http://bugzilla.gnome.org">bugzilla= .gnome.org</a> product, but is it worth keeping these instructions on this = already long page?<br> <br>2-<br></div><div>With the introduction of a classic mode built on gnome= -shell extensions, do we need instructions for gnome-shell extensions?<br>= <br>3-<br></div><div>Current instructions ask for reporters to add the trac= es as an attachment. I've noticed that bugzilla recognizes such text fi= les as binary files.<br> <br>Also, I've seen reports where traces shows up in the description, e= xpandable in line, instead of being an ordinary attachment. Example: <a hre= f=3D"https://bugzilla.gnome.org/show_bug.cgi?id=3D594425">https://bugzilla.= gnome.org/show_bug.cgi?id=3D594425</a> I don't know how to do that, but= it looks like something we should instruct reporters to do instead.<br> </div></div></div></div> --f46d044286ca9dc55d04d915f8a4-- --===============5182808500417582255== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ gnome-bugsquad mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-bugsquad --===============5182808500417582255==--